[ClusterLabs] Antw: [EXT] resource start after network reconnected
Ulrich.Windl at rz.uni-regensburg.de
Mon Nov 22 02:46:38 EST 2021
>>> "john tillman" <johnt at panix.com> schrieb am 18.11.2021 um 20:33 in
<28a37aa15622fa5ebd2f4d221e4eb6a0.squirrel at mail.panix.com>:
> Greetings all,
> preamble: RHEL8, PCS 0.10.8, COROSYNC 3.1.0, PACEMAKER 2.0.5
> I have a mysql resource, cloned, that is behaving the way I wanted. When
> the node it is on is unplugged from the network quorum is lost and the
> mysqld service stops. Great. Oh, and fencing is disabled.
The SLES HA manual makes it rather simple:
Important: No Support Without STONITH
You must have a node fencing mechanism for your cluster.
> When the network connectivity is restored I'd like it to restart but it
> doesn't. What needs to be done to make this happen automatically? Or
> what section of the doc should reread more thoroughly?
> When mysql is stopped because of the above, if I run "pcs resource
> refresh" it starts? Any ideas why the "refresh" would do that?
> It is definitely that call to refresh that triggers the start because I've
> run a handful of tests and the time between reconnecting the network and
> pcs resource refresh call varied by as much as 10 minutes.
> Any suggestion would be appreciated.
> Manage your subscription:
> ClusterLabs home: https://www.clusterlabs.org/
More information about the Users