| commit | cb94eba157679574c05d85f05828195e4099f2ba | |
| author | Martin Schwenke <martin@meltin.net> | |
| Fri, 25 Jul 2014 06:56:57 +0000 (25 16:56 +1000) | ||
| committer | Amitay Isaacs <amitay@samba.org> | |
| Tue, 29 Jul 2014 05:38:13 +0000 (29 07:38 +0200) | ||
| tree | ffafe9a165704ae0c5d8e347ad72bd49f91d4f35 | treesnapshot (tar.gz zip) |
| parent | d697c9fdcb9d1d08fa80fc78a299690c8114917c | commitdiff |
ctdb-eventscripts: Remove NAT gateway "monitor" event
This event was introduced to handle misconfiguration. For example,
where all nodes where configured as NAT gateway slaves.
However, this event can fail when there are performance issues and
capabilities can't be retrieved from a remote node. The problem is
most likely with the remote node, so marking the local node UNHEALTHY
is probably a mistake.
Having a NAT gateway master node only matters in "ipreallocated", so
leave it to do the checking. Given that a node will run
"ipreallocated" as part of the first recovery, this should cause
misconfigurations to be detected nice and early.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
This event was introduced to handle misconfiguration. For example,
where all nodes where configured as NAT gateway slaves.
However, this event can fail when there are performance issues and
capabilities can't be retrieved from a remote node. The problem is
most likely with the remote node, so marking the local node UNHEALTHY
is probably a mistake.
Having a NAT gateway master node only matters in "ipreallocated", so
leave it to do the checking. Given that a node will run
"ipreallocated" as part of the first recovery, this should cause
misconfigurations to be detected nice and early.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>