summaryrefslogtreecommitdiffstats
path: root/ctdb/lib/talloc/talloc.c
diff options
context:
space:
mode:
authorRonnie Sahlberg <sahlberg@ronnie>2007-07-09 12:33:00 +1000
committerRonnie Sahlberg <sahlberg@ronnie>2007-07-09 12:33:00 +1000
commit3499c8c673e468be589a5ef6cce31b08d8b489cc (patch)
tree1407cc97698c1e0e19e6d3541c5ed4f429fb4a04 /ctdb/lib/talloc/talloc.c
parent55a4a5def3440d7cc5d793696b0454f03e4925e7 (diff)
downloadsamba-3499c8c673e468be589a5ef6cce31b08d8b489cc.tar.gz
samba-3499c8c673e468be589a5ef6cce31b08d8b489cc.tar.xz
samba-3499c8c673e468be589a5ef6cce31b08d8b489cc.zip
when checking the nodemap flags for consitency while monitoring the
cluster, we cant check that both the BANNED and the DISCONNECTED flags are both set at the same time since if a node becomes banned just before it is DISCONNECTED there is no guarantee that all other nodes will have seen the BANNED flag. So we must first check the DISCONNECTED flag only and only if the DISCONNECTED flag is not set should we check the BANNED flag. othervise this can cause a recovery loop while some nodes thing the disconnected node is DISCONNECTED|BANNED and other think it is just DISCONNECTED (This used to be ctdb commit 0967b2fff376ead631d98e78b3a97253fc109c69)
Diffstat (limited to 'ctdb/lib/talloc/talloc.c')
0 files changed, 0 insertions, 0 deletions