summaryrefslogtreecommitdiffstats
path: root/extras
diff options
context:
space:
mode:
authorPranith Kumar K <pkarampu@redhat.com>2017-05-24 22:30:29 +0530
committerPranith Kumar Karampuri <pkarampu@redhat.com>2017-05-27 16:00:50 +0000
commitbea02e26a3967a6e679e30fbb77ecfeff1e71f37 (patch)
treec34f9d1d857e9ba7078bf78b3e21d43c2ae86d7b /extras
parent3ca5ae2f3bff2371042b607b8e8a218bf316b48c (diff)
features/shard: Handle offset in appending writes
When a file is opened with append, all writes are appended at the end of file irrespective of the offset given in the write syscall. This needs to be considered in shard size update function and also for choosing which shard to write to. At the moment shard piggybacks on queuing from write-behind xlator for ordering of the operations. So if write-behind is disabled and two parallel appending-writes come both of which can increase the file size beyond shard-size the file will be corrupted. BUG: 1455301 Change-Id: I9007e6a39098ab0b5d5386367bd07eb5f89cb09e Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: https://review.gluster.org/17387 Smoke: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Diffstat (limited to 'extras')
-rw-r--r--extras/group-gluster-block1
1 files changed, 0 insertions, 1 deletions
diff --git a/extras/group-gluster-block b/extras/group-gluster-block
index 0753d26b3ca..a4a6367920b 100644
--- a/extras/group-gluster-block
+++ b/extras/group-gluster-block
@@ -2,7 +2,6 @@ performance.quick-read=off
performance.read-ahead=off
performance.io-cache=off
performance.stat-prefetch=off
-performance.write-behind=off
performance.open-behind=off
performance.readdir-ahead=off
network.remote-dio=enable