summaryrefslogtreecommitdiffstats
path: root/libglusterfs/src/mem-types.h
diff options
context:
space:
mode:
authorGaurav Yadav <gyadav@redhat.com>2017-10-05 23:44:46 +0530
committerjiffin tony Thottan <jthottan@redhat.com>2017-11-06 12:16:15 +0000
commit1a1bdfbffc81981a80af40ebf000194d9bcd1bf0 (patch)
tree89801e2b992ed3697a2f4f1bf1117c754cb7e58d /libglusterfs/src/mem-types.h
parent4b480579320d6c594123e44fbedcba71f8815947 (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 'libglusterfs/src/mem-types.h')
-rw-r--r--libglusterfs/src/mem-types.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/libglusterfs/src/mem-types.h b/libglusterfs/src/mem-types.h
index d244fb528e3..85cb5d2b975 100644
--- a/libglusterfs/src/mem-types.h
+++ b/libglusterfs/src/mem-types.h
@@ -177,6 +177,7 @@ enum gf_common_mem_types_ {
gf_common_mt_pthread_t,
gf_common_ping_local_t,
gf_common_volfile_t,
+ gf_common_mt_mgmt_v3_lock_timer_t,
gf_common_mt_end
};
#endif