3b5f4de692
tcmu-runner is not going to open block with O_SYNC anymore so writes have a chance of getting cached in write-behind when that happens, there is a chance that on failover some data could be stuck in cache and be lost. BUG: 1485962 Change-Id: If9835d914821dfc4ff432dc96775677a55d2918f Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: https://review.gluster.org/18120 CentOS-regression: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Vijay Bellur <vbellur@redhat.com> Smoke: Gluster Build System <jenkins@build.gluster.org> Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>
19 lines
492 B
Plaintext
19 lines
492 B
Plaintext
performance.quick-read=off
|
|
performance.read-ahead=off
|
|
performance.io-cache=off
|
|
performance.stat-prefetch=off
|
|
performance.open-behind=off
|
|
performance.readdir-ahead=off
|
|
performance.strict-o-direct=on
|
|
network.remote-dio=disable
|
|
cluster.eager-lock=disable
|
|
cluster.quorum-type=auto
|
|
cluster.data-self-heal-algorithm=full
|
|
cluster.locking-scheme=granular
|
|
cluster.shd-max-threads=8
|
|
cluster.shd-wait-qlength=10000
|
|
features.shard=on
|
|
features.shard-block-size=64MB
|
|
user.cifs=off
|
|
server.allow-insecure=on
|