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: | glusterd | Assignee: | Avra Sengupta <asengupt> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | pre-release | CC: | 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: |
|
||||||
shylesh, can you check if this happens on master/3.3.0 release? (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. Avra, this should be addressed by synctask'izing the rebalance commands. |
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.