[ClusterLabs] resource start after network reconnected
hunter86_bg at yahoo.com
Sat Nov 20 15:33:26 EST 2021
You can also use this 3rd node to provide iSCSI and then the SBD will be disk-full :D . The good thing about this type of setup is that you do won't need to put location constraints for the 3rd node.
Also, check the ping resource -> you can set it up to "kick-out" all resources on failure of ping to a specific ip (for example the gateway). Once the network is restored, the node automatically becomes eligible to host the resources.
Also consider more advanced resource agents like ocf:heartbeat:mysql to control your mysql/mariadb database and also a replication between a primary and secondary (a.k.a master-slave ) replication.
В петък, 19 ноември 2021 г., 21:46:22 Гринуич+2, john tillman <johnt at panix.com> написа:
> On Fri, Nov 19, 2021 at 11:26:01AM -0500, john tillman wrote:
>> Anyone have any other ideas for a configuration setting that will
>> effectively do whatever 'pcs resource refresh' is doing when quorum is
> Since you have three nodes you may want to use the third node as QDevice
> After that SBD can be configured in diskless mode to reset the node that
> loses quorum:
Thank you. I'll look into using the Qdevice in the next release. For
now, I just have the three nodes with "vanilla" cluster packages.
> Manage your subscription:
> ClusterLabs home: https://www.clusterlabs.org/
Manage your subscription:
ClusterLabs home: https://www.clusterlabs.org/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users