summaryrefslogtreecommitdiffstats
path: root/source3/include
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2014-05-23 21:58:55 +1000
committerAmitay Isaacs <amitay@samba.org>2014-05-29 05:59:37 +0200
commit4dd382296d3e78000713ab0ac1f8e531e25857cc (patch)
tree30f8b27375004c4c28bfbecdb341c4d713ecd3eb /source3/include
parentf2ef23cd5f227d2da2f032a2a56fbdd4d105b137 (diff)
downloadsamba-4dd382296d3e78000713ab0ac1f8e531e25857cc.tar.gz
samba-4dd382296d3e78000713ab0ac1f8e531e25857cc.tar.xz
samba-4dd382296d3e78000713ab0ac1f8e531e25857cc.zip
ctdb-tools-ctdb: Make natgwlist and lvsmaster more resilient
Recent changes have caused these commands to attempt to get capabilities from all nodes before doing further filtering. This means that capabilities are unnecessarily fetched from nodes that are unlikely to be the master. If such a node does not answer the control then many nodes can fail to calculate the master node. In the case of natgwlist this will cause "monitor" events to fail resulting in unhealthy nodes. Restore the behaviour where capabilities are only fetched for a node that will be the master if it has the desired flags. Although this masks a problem where a connected node is not replying, it can help to avoid an outage in some cases. Add supporting tests and infrastructure. Infrastructure just lets a timeout be faked - just for ctdb_ctrl_getcapabilities_stub() so far. First test checks that this infrastructure works if the first node times out in natgwlist. Second test checks the case worked around by the above fix - that is, no failure when a node with PNN beyond the NATGW master can time out. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> Autobuild-User(master): Amitay Isaacs <amitay@samba.org> Autobuild-Date(master): Thu May 29 05:59:37 CEST 2014 on sn-devel-104
Diffstat (limited to 'source3/include')
0 files changed, 0 insertions, 0 deletions