Bug 1291262
| Summary: | glusterd: fix gluster volume sync after successful deletion | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Prasanna Kumar Kalever <prasanna.kalever> |
| Component: | glusterd | Assignee: | Sanju <srakonde> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | atumball, bugs |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 09:56:53 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: | |||
REVIEW: http://review.gluster.org/12963 (glusterd: fix gluster volume sync after successful deletion) posted (#1) for review on master by Prasanna Kumar Kalever (pkalever) This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Looks like these issues are now resolved. Would be good to clarify and mark this CLOSED. commit 0b450b8b35 has fixed this issue. So, closing this bug as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1605077 (which is used to track the bug, while the patch has posted for review). Thanks, Sanju *** This bug has been marked as a duplicate of bug 1605077 *** |
Description of problem: Problem: Say, we have a 100 node gluster pool, on which we created a volume 'NEWVOL', we have used the volume and now it's time for deletion NEWVOL, unfortunately say one among 100 nodes went down, we all know still we can delete the volume from any of the remaining 99 nodes, and the deletion will be successful Current Behaviour: Now, after some time the node which was down while performing volume deletion operation comes up and volume NEWVOL is re-spawned/synced to all the rest 99 nodes, which is not expected and may create problems Expected Behaviour: Up on node which was down comes up it should delete the volume by looking at peers Version-Release number of selected component (if applicable): mainline