Bug 1223739 - Quota: Do not allow set/unset of quota limit in heterogeneous cluster
Summary: Quota: Do not allow set/unset of quota limit in heterogeneous cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1226158
TreeView+ depends on / blocked
 
Reported: 2015-05-21 11:22 UTC by Vijaikumar Mallikarjuna
Modified: 2016-06-16 13:03 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1226153 1226158 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:03:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Vijaikumar Mallikarjuna 2015-05-21 11:22:26 UTC 
There is change in quota.conf format in release-3.7. In a heterogeneous cluster if the quota limit is changed, this can cause a hand-shake problem when glusterd is restarted.

Do not allow setting/removing quota limit in heterogeneous cluster
Comment 1 Anand Avati 2015-05-22 08:44:31 UTC 
REVIEW: http://review.gluster.org/10889 (quota: quota.conf backward compatibility fix) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
Comment 2 Anand Avati 2015-05-28 06:55:31 UTC 
REVIEW: http://review.gluster.org/10889 (quota: quota.conf backward compatibility fix) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
Comment 3 Anand Avati 2015-05-29 01:57:46 UTC 
COMMIT: http://review.gluster.org/10889 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit b7f05e64f615a12e6487eab64544b8f92a6037ae
Author: vmallika <vmallika>
Date:   Fri May 22 14:04:31 2015 +0530

    quota: quota.conf backward compatibility fix
    
    In release-3.7 the format of quota.conf is changed.
    There is a backward compatibility issues during upgrade
    1) There can be an issue when peer sync between node-3.6 and node-3.7
    2) If the user sets/removes limit, there is will different format of
       file in node-3.6 and node-3.7
    
    This patch fixes the issue:
    1) restrict the user to execute command quota enable, limit-usage, remove
    2) write quota.conf in older format if op-version is less than 3.6
    
    Change-Id: Ib76f5a0a85394642159607a105cacda743e7d26b
    BUG: 1223739
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/10889
    Tested-by: NetBSD Build System
    Reviewed-by: Krishnan Parthasarathi <kparthas>
Comment 4 Niels de Vos 2015-06-02 08:20:20 UTC 
The required changes to fix this bug have not made it into glusterfs-3.7.1. This bug is now getting tracked for glusterfs-3.7.2.
Comment 5 Niels de Vos 2015-06-20 10:08:26 UTC 
Unfortunately glusterfs-3.7.2 did not contain a code change that was associated with this bug report. This bug is now proposed to be a blocker for glusterfs-3.7.3.
Comment 6 Vijaikumar Mallikarjuna 2015-06-22 06:57:39 UTC 
upstream patch: http://review.gluster.org/#/c/10889/
release-3.7 patch: http://review.gluster.org/#/c/10985/
Comment 7 Niels de Vos 2016-06-16 13:03:49 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Note You need to log in before you can comment on or make changes to this bug.