[ClusterLabs] resource start after network reconnected
arvidjaar at gmail.com
Fri Nov 19 00:38:13 EST 2021
On 18.11.2021 22:33, john tillman wrote:
> 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.
> 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?
You provided zero information about your setup and how you configured pacemaker to stop mysqld on network connectivity loss, so it is rather hard to guess.
Logs covering period when you unplug network, and later plug again, could be also helpful.
> 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