[ClusterLabs] How to make a node persistent active in pacemaker-corosync?

Klaus Wenninger kwenning at redhat.com
Mon Dec 11 06:47:59 EST 2017


On 12/10/2017 12:10 PM, Ricardo Cristian Ramirez wrote:
> Hi all,
>
> I have an active-passive pacemaker-corosync configuration.
>
> When a node is powered up before the other one, it becomes active, and
> the node, which is powered up second, becomes passive.
>
> (For a node, being active means that to run resources on itself.)
>
> What I want is that to have a node which is persistenly active while
> it is powered up.
>
> For example, say we want node0 as persistent active node, and node1 as
> passive node.
>
> Scenario:
>
>     Power up node1 (node1 is active)
>     Power up node0 (node0 is active, node1 is passive)
>
> What is the correct way of doing this?
>

If I'm getting you right resource stickiness would be the feature
you are searching for:
http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_prevent_resources_from_moving_after_recovery.html

Regards,
Klaus

>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org





More information about the Users mailing list