diff options
| author | Gaurav Yadav <gyadav@redhat.com> | 2017-10-05 23:44:46 +0530 |
|---|---|---|
| committer | jiffin tony Thottan <jthottan@redhat.com> | 2017-11-06 12:16:15 +0000 |
| commit | 1a1bdfbffc81981a80af40ebf000194d9bcd1bf0 (patch) | |
| tree | 89801e2b992ed3697a2f4f1bf1117c754cb7e58d /extras | |
| parent | 4b480579320d6c594123e44fbedcba71f8815947 (diff) | |
glusterd : introduce timer in mgmt_v3_lock
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
>mainline patch : https://review.gluster.org/#/c/18437/
Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
BUG: 1503239
Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
Diffstat (limited to 'extras')
| -rw-r--r-- | extras/glusterd.vol.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/extras/glusterd.vol.in b/extras/glusterd.vol.in index 957b277801c..5338aa25b0d 100644 --- a/extras/glusterd.vol.in +++ b/extras/glusterd.vol.in @@ -7,6 +7,7 @@ volume management 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 end-volume |