REVIEW: http://review.gluster.org/5892 (rpc/rpc-lib: rpcsvc should reply when rpc_err is set) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/5892 (rpc/rpc-lib: rpcsvc should reply when rpc_err is set) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/5892 committed in master by Anand Avati (avati) ------ commit 015f1fd479b42b79aac46a5b8d9980c770a32d9e Author: Pranith Kumar K <pkarampu> Date: Tue Sep 10 19:13:47 2013 +0530 rpc/rpc-lib: rpcsvc should reply when rpc_err is set Problem: When requests are received on a connection before setvolume is done, creating frame from the requests fail because there is no association of the transport with the conn(i.e. xl_private). xl_private is set only on set_volume. In such cases error response is not sent from server xlator to that request because of which operations on mount point are hanging. Fix: Set actor return value to RPCSVC_ACTOR_ERROR so that response is sent even in these cases. Change-Id: I74d7bc6849fde6c734008d67c1f4bc9d9f7a84f9 BUG: 1006367 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/5892 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
REVIEW: http://review.gluster.org/5956 (protocol/client: Add explicit states for connection sequence) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/5956 (protocol/client: Add explicit states for connection sequence) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/5956 (protocol/client: Add explicit states for connection sequence) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/5956 (protocol/client: Add explicit states for connection sequence) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
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.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
REVIEW: http://review.gluster.org/5956 (protocol/client: Add explicit states for connection sequence) posted (#5) for review on master by Harshavardhana (harsha)