REVIEW: http://review.gluster.org/11658 (glusterd: do not pass volinfo in glusterd_svc_manager function) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
http://review.gluster.org/11658 patch solving this problem which is already merged. but this problem might hit again, Assigning to quota team member.
REVIEW: http://review.gluster.org/11990 (rpc: invoke rpc_submit cbk function in separate thread) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/11990 (rpc: invoke rpc_submit cbk function in separate thread) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/11990 (cli: on error invoke cli_cmd_broadcast_response function in separate thread) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/11990 (cli: on error invoke cli_cmd_broadcast_response function in separate thread) posted (#4) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/11990 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 7a27810aecce6e014100dbbc3c7961d769082c1e Author: vmallika <vmallika> Date: Mon Aug 24 08:07:14 2015 +0530 cli: on error invoke cli_cmd_broadcast_response function in separate thread There is a problem in current CLI framework CLI holds the lock when processing command. When processing quota list command, below sequence of steps executed in the same thread and causing deadlock 1) CLI holds the lock 2) Send rpc_clnt_submit request to quotad for quota usage 3) If quotad is down, rpc_clnt_submit invokes cbk function with error 4) cbk function cli_quotad_getlimit_cbk tries to hold lock to broadcast the results and hangs, because same thread has already holding the lock This patch fixes the problem by creating seperate thread for broadcasting the result Change-Id: I53be006eadf6aaf348083d9168535530d70a8ab3 BUG: 1242819 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/11990 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Krishnan Parthasarathi <kparthas>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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