[Gluster-devel] Afr handling dir fop failures on all nodes gracefully.

Pranith Kumar K pkarampu at redhat.com
Wed Jan 9 12:28:06 UTC 2013

          Attaching the steps to re-create the issue.
As part of Entry transaction, before performing 
create/mknod/mkdir/rmdir/unlink/link/symlink/rename fops, afr takes 
appropriate entry locks and then performs pre-op. If the fop fails on 
all nodes then the changelog leaves the directory in 'FOOL' state. 
Because of this the subsequent self-heal will be conservative merge, 
which may bring back the files that were already deleted leading to 
duplicate entries across distribute subvolumes.

We need to improve afr-transaction to handle this case gracefully.

Sending this mail to start the discussion towards a solution. Please 
feel free to contribute.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.t
Type: text/troff
Size: 1119 bytes
Desc: not available
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20130109/f9bd00ce/attachment-0001.bin>

More information about the Gluster-devel mailing list