summaryrefslogtreecommitdiffstats
path: root/ctdb/.bzrignore
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2007-04-19 10:03:20 +1000
committerAndrew Tridgell <tridge@samba.org>2007-04-19 10:03:20 +1000
commitfde5a66531af99c6d6ef665ccbfbb4944bdefdd3 (patch)
tree74d96c5b87c05e70bf696bd4319102dc12fdf221 /ctdb/.bzrignore
parenta3ab61b384c90858df6af52f386daa71025767f4 (diff)
downloadsamba-fde5a66531af99c6d6ef665ccbfbb4944bdefdd3.tar.gz
samba-fde5a66531af99c6d6ef665ccbfbb4944bdefdd3.tar.xz
samba-fde5a66531af99c6d6ef665ccbfbb4944bdefdd3.zip
avoid a deadlock the fetch_lock code. The deadlock could happen when
a client held the chainlock, and the daemon received a dmaster reply at the same time. The daemon would not be able to process the dmaster reply, due to the lock, but the fetch lock cannot make progres until the dmaster reply is processed. The solution is to not hold the lock in the client while talking to the daemon. The client has to retry the lock after the record has migrated. This means that forward progress is not guaranteed. We'll have to see if that matters in practice. (This used to be ctdb commit 737e5a1253cb048222c595a474aff71c99fc554f)
Diffstat (limited to 'ctdb/.bzrignore')
-rw-r--r--ctdb/.bzrignore4
1 files changed, 4 insertions, 0 deletions
diff --git a/ctdb/.bzrignore b/ctdb/.bzrignore
index a6fe6dc21e3..9887e239900 100644
--- a/ctdb/.bzrignore
+++ b/ctdb/.bzrignore
@@ -10,3 +10,7 @@ config.h
config.h.in
nodes-ssh.txt
TAGS
+ctdb-0
+ctdb-1
+ctdb-2
+ctdb-3