Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 822784

Summary: Rebalance status command does not respond if network is down or power failure on any of the nodes in the cluster
Product: [Community] GlusterFS Reporter: shylesh <shmohan>
Component: glusterdAssignee: Avra Sengupta <asengupt>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: pre-releaseCC: amarts, gluster-bugs, vbellur
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 852295 (view as bug list) Environment:
Last Closed: 2013-07-24 17:51:10 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:
Bug Depends On:    
Bug Blocks: 852295, 858476    
Attachments:
Description Flags
fsm logs none

Description shylesh 2012-05-18 07:08:31 UTC
Created attachment 585348 [details]
fsm logs

Description of problem:
Issuing rebalance status command does not responds if network fails or power failure occurs on any of the node in the cluster.

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


How reproducible:


Steps to Reproduce:
1. created a distributed-replicate volume and fill up with some data
2. add-brick and initiate rebalance .
3. check the status 
4. Now bring down network or reboot any of the machine in the cluster
5. Now check the status
  
Actual results:

status command will not respond anything , it waits for some time and comes back with return value 234.

Expected results:


Additional info:

Attaching the fsm-logs.

Comment 1 Amar Tumballi 2012-07-11 05:22:22 UTC
shylesh, can you check if this happens on master/3.3.0 release?

Comment 2 shylesh 2012-07-11 11:18:39 UTC
 (In reply to comment #1)
> shylesh, can you check if this happens on master/3.3.0 release?

Yes amar this issue is still reproducible on latest master.

Comment 3 Amar Tumballi 2013-02-06 04:50:59 UTC
Avra, this should be addressed by synctask'izing the rebalance commands.