Bug 1649252 - duplicate performance.cache-size with different values
Summary: duplicate performance.cache-size with different values
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: io-cache
Version: mainline
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Csaba Henk
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On: 1589705
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-13 09:10 UTC by Davide
Modified: 2019-11-04 07:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-04 07:45:17 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Davide 2018-11-13 09:10:23 UTC 
Description of problem:
duplicate performance.cache-size with different values if you run gluster volume get volname all

performance.cache-size                  32MB
...
performance.cache-size                  128MB

Version-Release number of selected component (if applicable):
in gluster 4.1.5

How reproducible:
gluster volume get volname all

Steps to Reproduce:
1. create a volume
2. gluster volume get volname all
3. 

Actual results:
This is a bug with naming the options. Two xlators io-cache and quick-read have same keys listed in glusterd-volume-set.c. can you file a bug?

Expected results:
only one valid entry/value

Additional info:
Comment 2 Raghavendra G 2018-11-13 09:17:54 UTC 
https://review.gluster.org/#/c/glusterfs/+/20218/
Comment 3 Atin Mukherjee 2019-04-19 06:34:13 UTC 
This is a RHBZ reported by an upstream user and product was selected wrong.
Comment 4 Amar Tumballi 2019-07-05 08:43:05 UTC 
https://review.gluster.org/22539
Comment 5 Nithya Balachandran 2019-11-04 07:45:17 UTC 
(In reply to Amar Tumballi from comment #4)
> https://review.gluster.org/22539

This patch has been merged in master. Closing this BZ.
Note You need to log in before you can comment on or make changes to this bug.