From 1a1bdfbffc81981a80af40ebf000194d9bcd1bf0 Mon Sep 17 00:00:00 2001 From: Gaurav Yadav Date: Thu, 5 Oct 2017 23:44:46 +0530 Subject: 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 --- extras/glusterd.vol.in | 1 + 1 file changed, 1 insertion(+) (limited to 'extras') 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 -- cgit