summaryrefslogtreecommitdiffstats
path: root/extras
diff options
context:
space:
mode:
authorGaurav Yadav <gyadav@redhat.com>2017-10-05 23:44:46 +0530
committerShyamsundar Ranganathan <srangana@redhat.com>2018-03-20 13:58:38 +0000
commit9bd5c119076577b1029c7f451d19baa9a735a850 (patch)
tree16584311d0e8233aad585a7eaa08e60fecfe9669 /extras
parent616c5bf733e64df0f9f6822180d62418688cfc1c (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 >Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843 >BUG: 1499004 >Signed-off-by: Gaurav Yadav <gyadav@redhat.com> Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843 BUG: 1557304 Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
Diffstat (limited to 'extras')
-rw-r--r--extras/glusterd.vol.in1
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