Bug 852295 - Rebalance status command does not respond if network is down or power failure on any of the nodes in the cluster
Summary: Rebalance status command does not respond if network is down or power failure...
Keywords:
Status: CLOSED DUPLICATE of bug 852147
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: krishnan parthasarathi
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On: 822784
Blocks: 858476
TreeView+ depends on / blocked
 
Reported: 2012-08-28 07:08 UTC by Vidya Sakar
Modified: 2015-11-03 23:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 822784
: 858476 (view as bug list)
Environment:
Last Closed: 2013-01-09 07:55:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Vidya Sakar 2012-08-28 07:08:16 UTC
+++ This bug was initially created as a clone of Bug #822784 +++

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.

--- Additional comment from amarts on 2012-07-11 01:22:22 EDT ---

shylesh, can you check if this happens on master/3.3.0 release?

--- Additional comment from shmohan on 2012-07-11 07:18:39 EDT ---

 (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 2 krishnan parthasarathi 2013-01-09 07:55:48 UTC

*** This bug has been marked as a duplicate of bug 852147 ***


Note You need to log in before you can comment on or make changes to this bug.