[Bugs] [Bug 1291262] New: glusterd: fix gluster volume sync after successful deletion

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1291262

            Bug ID: 1291262
           Summary: glusterd: fix gluster volume sync after successful
                    deletion
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: prasanna.kalever at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.