Description of problem: network.compression.min-size: 50 network.compression.compression-level: 5 Above options are set on 'distvol'.. [root@desktop77 distvol]# gluster v i distvol Volume Name: distvol Type: Distribute Volume ID: e9e82efe-d5eb-4f74-aa71-bdfe9d94fb9f Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: desktop77.example.com:/brick2/dist1 Brick2: desktop78.example.com:/brick2/dist2 Options Reconfigured: network.compression.min-size: 50 network.compression.compression-level: 5 features.quota: on network.compression.mode: server Try to reset the options.. [root@desktop77 distvol]# gluster volume reset distvol network.compression volume reset: success: reset volume successful The command was successful, how-ever it failed to reflect.. [root@desktop77 distvol]# gluster v i distvol Volume Name: distvol Type: Distribute Volume ID: e9e82efe-d5eb-4f74-aa71-bdfe9d94fb9f Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: desktop77.example.com:/brick2/dist1 Brick2: desktop78.example.com:/brick2/dist2 Options Reconfigured: network.compression.min-size: 50 network.compression.compression-level: 5 features.quota: on network.compression.mode: server [root@desktop77 distvol]# Version-Release number of selected component (if applicable): [root@desktop77 distvol]# rpm -qa |grep gluster glusterfs-3.5.0-0.5.beta3.fc21.x86_64 glusterfs-server-3.5.0-0.5.beta3.fc21.x86_64 glusterfs-devel-3.5.0-0.5.beta3.fc21.x86_64 glusterfs-cli-3.5.0-0.5.beta3.fc21.x86_64 samba-vfs-glusterfs-4.1.4-1.fc20.x86_64 glusterfs-api-3.5.0-0.5.beta3.fc21.x86_64 glusterfs-libs-3.5.0-0.5.beta3.fc21.x86_64 glusterfs-fuse-3.5.0-0.5.beta3.fc21.x86_64 [root@desktop77 distvol]# How reproducible: Always Steps to Reproduce: As shown above. Actual results: It failed to reset the options.. Expected results: The network compression options should come back to default.
I feel this bug is a DUP of https://bugzilla.redhat.com/show_bug.cgi?id=1065655
Humble, Check for comment1
(In reply to SATHEESARAN from comment #1) > I feel this bug is a DUP of > https://bugzilla.redhat.com/show_bug.cgi?id=1065655 yep, looks like:
Does this need a fix backported to 3.5.x ?
As all the duplicates are CLOSED_CURRENTRELEASE, calling this the same.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days