[ClusterLabs] Autostart/Enabling of Pacemaker and corosync
Strahil Nikolov
hunter86_bg at yahoo.com
Mon Apr 26 14:04:41 EDT 2021
I prefer that the stack is auto enabled. Imagine that you got a DB that is replicated and primary DB node is fenced.
You would like that node to join the cluster and if possible to sync with the new primary instead of staying down.
One such example is the SAP HANA DB. Imagine that the current primary node looses storage and it failed to commit all transactions to disk. Without replication you will endure data loss for the last 1-2 minutes (depends on your monitoring interval) unless you got a replication.
Yet, there are cases where the previously fenced node joins the cluster and due to hardware issues causes performance degradation on the current master.
Both cases have their benefits and drawbacks and you have to weight them all before taking that decision.
Best Regards,Strahil Nikolov
On Mon, Apr 26, 2021 at 20:04, Moneta, Howard<Howard.Moneta at csaa.com> wrote: <!--#yiv6119479942 _filtered {} _filtered {}#yiv6119479942 #yiv6119479942 p.yiv6119479942MsoNormal, #yiv6119479942 li.yiv6119479942MsoNormal, #yiv6119479942 div.yiv6119479942MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv6119479942 a:link, #yiv6119479942 span.yiv6119479942MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv6119479942 a:visited, #yiv6119479942 span.yiv6119479942MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv6119479942 span.yiv6119479942EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv6119479942 .yiv6119479942MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered {}#yiv6119479942 div.yiv6119479942WordSection1 {}-->
Hello community. I have read that it is not recommended to set Pacemaker and corosync to enabled/auto start on the nodes. Is this how people have it configured? If a computer restarts unexpectedly, is it better to manually investigate first or allow the node to come back online and rejoin the cluster automaticly in order to minimize downtime? If the auto start is not enabled, how do you handle patching? I’m using Pacemaker with PAF, PostgreSQL Automatic Failover. I had thought to follow the published guidance and not set those processes to enabled but other coworkers are resisting and saying that the systems should be configured to recover by themselves around patching or even a temporary unplanned network/virtualization glitch.
Thanks,
Howard
This message may contain information, including personally identifiable information that is confidential, privileged, or otherwise legally protected. If you are not the intended recipient, please immediately notify the sender and delete this message without copying, disclosing, or distributing it.
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20210426/578275c4/attachment-0001.htm>
More information about the Users
mailing list