REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#7) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#8) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#9) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#10) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#11) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#12) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#13) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#14) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#15) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status.) posted (#16) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status) posted (#17) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status) posted (#18) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status) posted (#19) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status) posted (#20) for review on master by Sachin Pandit (spandit)

REVIEW: http://review.gluster.org/7456 (glusterd/status : First fetch the snapcount and then send the rpc call for individual snapshots for snapshot status) posted (#21) for review on master by Sachin Pandit (spandit)

COMMIT: http://review.gluster.org/7456 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit 31520d9334f9a40aa329d54651bca7e2c2e5d545
Author: Sachin Pandit <spandit>
Date:   Tue Apr 1 09:20:05 2014 +0530

    glusterd/status : First fetch the snapcount and then send the rpc call
    for individual snapshots for snapshot status
    
    Problem :
    
    Initially, we used to do all the calculation in the
    glusterd side, once all the information related to
    snap was fetched, it was aggregated into one
    dictionary and that was sent back to CLI. Problem
    with this approach was, when number of snapshots
    are very high then CLI will timeout.
    
    Solution:
    
    First fetch snapcount and snapname from glusterd,
    then make a individual calls using the snapname
    fetched. This will resolve the timeout problem.
    
    Change-Id: I32609b3898ed227c804dd4d8ee4516f081240756
    BUG: 1087676
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/7456
    Reviewed-by: Avra Sengupta <asengupt>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users