Bug 1198076

Summary: CIFS: [USS]: After upgrade gluster volume status command times out if 256 snapshots preexists
Product: [Community] GlusterFS Reporter: Avra Sengupta <asengupt>
Component: glusterdAssignee: Avra Sengupta <asengupt>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: pre-releaseCC: asengupt, bugs, gluster-bugs, nlevinki, nsathyan, rcyriac, rhs-bugs, ssamanta, storage-qa-internal, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: USS
Fixed In Version: glusterfs-3.7.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1196557 Environment:
Last Closed: 2015-05-14 17:29:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1196557    
Bug Blocks:    

Comment 1 Anand Avati 2015-03-03 11:53:49 UTC
REVIEW: http://review.gluster.org/9791 (glusterd: Start quotad before spawning bricks during glusterd restart) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Avra Sengupta 2015-03-03 12:14:46 UTC
RCA: If a node that is running 256 bricks, and on which quotad is enabled, is restarted, the 256 bricks spawn first, followed by quotad. The bricks after spawning request glusterd for a volfile, and so does quotad. Initially a few bricks which were started first do receive the volfile, after which they try to communicate to quotad, but fail to do so as quotad is performing a blocking connect to glusterd and still waiting to recieve the volfile. glusterd meanwhile tries to repeatedly connect to the bricks it sent the volfile to, but fails to do so coz the bricks are still waiting on quotad. So we end up with a system where glusterd is waiting on some bricks, which are waiting on quotad, and quotad along with the rest of the bricks are waiting on glusterd.

Comment 3 Anand Avati 2015-03-04 14:14:32 UTC
COMMIT: http://review.gluster.org/9791 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit f82756b4909cebaf533570aec2b05ba55a7dcc95
Author: Avra Sengupta <asengupt>
Date:   Tue Mar 3 17:21:54 2015 +0530

    glusterd: Start quotad before spawning bricks during glusterd restart
    
    Change-Id: I66edc1b98b70a494e069df95a6f347634c8f862d
    BUG: 1198076
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/9791
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

Comment 4 Niels de Vos 2015-05-14 17:29:16 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:35:52 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:38:14 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:46:13 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user