Re: [ClusterLabs] resource start after network reconnected

2021-11-18 Thread Andrei Borzenkov
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

Re: [ClusterLabs] resource start after network reconnected

2021-11-18 Thread Valentin Vidić via Users
On Thu, Nov 18, 2021 at 03:42:48PM -0500, john tillman wrote: > I don't believe I can since I do not have a fencing device available. As this page explains, fencing is required for the cluster to behave correctly: https://www.alteeve.com/w/The_2-Node_Myth Can you share what kind of nodes are

Re: [ClusterLabs] resource start after network reconnected

2021-11-18 Thread john tillman
> On Thu, Nov 18, 2021 at 02:33:28PM -0500, john tillman wrote: >> 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

Re: [ClusterLabs] resource start after network reconnected

2021-11-18 Thread Valentin Vidić via Users
On Thu, Nov 18, 2021 at 02:33:28PM -0500, john tillman wrote: > 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

[ClusterLabs] resource start after network reconnected

2021-11-18 Thread john tillman
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