mirror of
https://github.com/gluster/glusterfs.git
synced 2026-02-06 18:48:16 +01:00
2b3e3ef08d
lookup-optimize doesn't provide any benefit for virtualized environments and gluster-block workloads, but it's known to cause corruption in some cases when sharding is also enabled and the volume is expanded or shrunk. For this reason, we disable lookup-optimize by default on those environments. Fixes: #2253 Change-Id: I25861aa50b335556a995a9c33318dd3afb41bf71 Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
26 lines
674 B
Plaintext
26 lines
674 B
Plaintext
performance.quick-read=off
|
|
performance.read-ahead=off
|
|
performance.io-cache=off
|
|
performance.low-prio-threads=32
|
|
network.remote-dio=disable
|
|
performance.strict-o-direct=on
|
|
cluster.eager-lock=enable
|
|
cluster.quorum-type=auto
|
|
cluster.server-quorum-type=server
|
|
cluster.data-self-heal-algorithm=full
|
|
cluster.locking-scheme=granular
|
|
cluster.shd-max-threads=8
|
|
cluster.shd-wait-qlength=10000
|
|
features.shard=on
|
|
user.cifs=off
|
|
cluster.choose-local=off
|
|
client.event-threads=4
|
|
server.event-threads=4
|
|
performance.client-io-threads=on
|
|
network.ping-timeout=20
|
|
server.tcp-user-timeout=20
|
|
server.keepalive-time=10
|
|
server.keepalive-interval=2
|
|
server.keepalive-count=5
|
|
cluster.lookup-optimize=off
|