Bug 986945

Summary:	Increase cli timeout for gluster volume heal info commands
Product:	[Community] GlusterFS	Reporter:	vsomyaju
Component:	cli	Assignee:	vsomyaju
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	pre-release	CC:	gluster-bugs, laurent.chouinard, nsathyan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.5.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-17 11:43:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description vsomyaju 2013-07-22 13:21:49 UTC

Description of problem:

gluster volume heal volume info commands gets the list of all files to be healed.
If number of files to be healed is very large, in that case, cli is timout is too early. Having a larger time can handle large number of files to be displayed.


Version-Release number of selected component (if applicable):


How reproducible:
Ofter

Steps to Reproduce:
1. Create a replicate volume
2. Kill one brick
3. Create large Number of files
4. execute gluster volume heal volume1 info command 

Actual results:
Another transaction is in progress.

Expected results:
If output can be obtained within 10 Minutes, it will be display the list of all files to be healed in that volume

Additional info:

Comment 1 Anand Avati 2013-07-22 13:33:56 UTC

REVIEW: http://review.gluster.org/5372 (cli: Increased timeout for gluster volume heal commnads) posted (#1) for review on master by venkatesh somyajulu (vsomyaju)

Comment 2 Anand Avati 2013-07-23 09:53:21 UTC

COMMIT: http://review.gluster.org/5372 committed in master by Anand Avati (avati) 
------
commit 50cfc2d8e814ec649283bbd058eebd779d213d4d
Author: Venkatesh Somyajulu <vsomyaju>
Date:   Mon Jul 22 19:00:53 2013 +0530

    cli: Increased timeout for gluster volume heal commnads
    
    Problem:
    If number of files are very large, then gluster volume heal
    volumename info commnads take large time. So timeout of 2
    minutes seems to be insufficient.
    
    Fix:
    Increased timeout to 10 minutes
    
    Change-Id: I5f847163e01c4afbb587b726833ad80183f1a928
    BUG: 986945
    Signed-off-by: Venkatesh Somyajulu <vsomyaju>
    Reviewed-on: http://review.gluster.org/5372
    Reviewed-by: Kaushal M <kaushal>
    Tested-by: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2014-04-17 11:43:57 UTC

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