614904fa7a
Problem: In a multinode environment, if two of the op-sm transactions are initiated on one of the receiver nodes at the same time, there might be a possibility that glusterd may end up in stale lock. Solution: During mgmt_v3_lock a registration is made to gf_timer_call_after which release the lock after certain period of time Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843 BUG: 1499004 Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
15 lines
454 B
Plaintext
15 lines
454 B
Plaintext
volume management
|
|
type mgmt/glusterd
|
|
option working-directory @GLUSTERD_WORKDIR@
|
|
option transport-type socket,rdma
|
|
option transport.socket.keepalive-time 10
|
|
option transport.socket.keepalive-interval 2
|
|
option transport.socket.read-fail-log off
|
|
option ping-timeout 0
|
|
option event-threads 1
|
|
# option lock-timer 180
|
|
# option transport.address-family inet6
|
|
# option base-port 49152
|
|
# option max-port 65535
|
|
end-volume
|