Bug 764852 (GLUSTER-3120)

Summary:	Provide connection timeout between cli and glusterd
Product:	[Community] GlusterFS	Reporter:	Vijay Bellur <vijay>
Component:	cli	Assignee:	Vijay Bellur <vbellur>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.1.4	CC:	amarts, gluster-bugs, rabhat, shireesh
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Vijay Bellur 2011-07-03 15:23:06 UTC

Currently, cli blocks for 120 seconds if glusterd is not running. Need a mechanism to reduce this timeout interval.

Comment 1 Anand Avati 2011-07-11 07:57:30 UTC

PATCH: http://patches.gluster.com/patch/7779 in release-3.1 (cli: Exit if glusterd is not operational in non-prompt modes)

Comment 2 Anand Avati 2011-07-11 08:07:58 UTC

PATCH: http://patches.gluster.com/patch/7761 in master (cli: Exit if glusterd is not operational in non-prompt modes)

Comment 3 Raghavendra Bhat 2011-07-29 03:51:53 UTC

Its fixed now. Checked with release-3.1 branch. And if glusterd is not running, then cli errors out with the error.


gluster volume create new bigbang:/tmp/new
Connection failed. Please check if gluster daemon is operational.

Comment 4 Anand Avati 2011-08-22 12:06:26 UTC

CHANGE: http://review.gluster.com/297 (Change-Id: Icab7965f570e3c422e5b18b89bc418f3598c2c4d) merged in release-3.2 by Vijay Bellur (vijay)