summaryrefslogtreecommitdiffstats
path: root/doc/admin-guide/en-US/markdown/admin_managing_volumes.md
diff options
context:
space:
mode:
authorPranith Kumar K <pkarampu@redhat.com>2013-07-03 05:23:46 +0530
committerVijay Bellur <vbellur@redhat.com>2013-07-03 00:40:08 -0700
commit29619b4ee78926160435da82f9db213161e040d4 (patch)
treecd147458271280b5344aa0b86d970c9de7c234c5 /doc/admin-guide/en-US/markdown/admin_managing_volumes.md
parent7fd38981278c8a51587f1db5b59f8cfeed5c6e5a (diff)
cluster/afr: post-op should complete before starting flush
Problem: At the moment afr-flush makes sure that a delayed post-op is woken up but it does not wait for it to complete the post-op before flush unwinds. These are the steps that are happening: 1) flush fop comes on an fd which wakes up a delayed post-op and continues with the flush fop. 2) post-op sends fsync on the wire. 3) flush completes and unwinds to fuse. 4) graph switch happens on the fuse mount disconnecting the old graph's client connections to bricks. 5) xattrop after fsync fails with ENOTCONN because the connections from old graph are taken down now. Fix: Wait for post-op to complete before starting to flush. We could make flush act similar to fsync (i.e.) wind flush as is but wait for post-op to complete before unwinding flush, but it is better to send flush as the final fop. So wind of flush will start after post-op is complete. Had to change fsync to accommodate this change. Change-Id: I93aa642647751969511718b0e137afbd067b388a BUG: 980548 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: http://review.gluster.org/5274 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Diffstat (limited to 'doc/admin-guide/en-US/markdown/admin_managing_volumes.md')
0 files changed, 0 insertions, 0 deletions