Bug 763553 (GLUSTER-1821) - peer probe hangs for 2 minutes if glusterd is not running on the remote host
Summary: peer probe hangs for 2 minutes if glusterd is not running on the remote host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1821
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-05 21:07 UTC by Vikas Gorur
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Vikas Gorur 2010-10-05 21:07:48 UTC 
[root@vikas-sb glusterfs]# date; /opt/glusterfs/git/sbin/gluster peer probe brick5; date
Tue Oct  5 14:00:06 PDT 2010
Probe failed
Tue Oct  5 14:02:06 PDT 2010

Most users when using this command would not wait two minutes and would think that the CLI is hung. CLI should detect that glusterd isn't running remotely and report the error immediately.

(showmount, which uses the same RPC mechanisms, for example immediately errors out if there is no NFS server running).
Comment 1 Vijay Bellur 2010-10-07 15:44:44 UTC 
Not a blocker as there exists a workaround.
Comment 2 Pranith Kumar K 2010-11-15 00:07:17 UTC 
hi Amar,
      Please re-assign this to me once rpc has the infra to fix this.

Pranith
Comment 3 Amar Tumballi 2011-09-07 15:05:15 UTC 
CHANGE: http://review.gluster.com/342 (so 'gluster peer probe' command doesn't
hang till timeout (120s),) merged in master by Anand Avati (avati)
Note You need to log in before you can comment on or make changes to this bug.