On Wed, 12 Apr 2017 09:19:06 +0200 Kristoffer Grönlund <[email protected]> wrote:
> Jehan-Guillaume de Rorthais <[email protected]> writes: > > > Hi, > > > >> >>> Kristoffer Grönlund <[email protected]> schrieb am 11.04.2017 um 15:30 > >> >>> in > >> Nachricht <[email protected]>: > >> > Hi all, > >> > > >> > I discovered today that a location constraint with score=INFINITY > >> > doesn't actually restrict resources to running only on particular > >> > nodes. From what I can tell, the constraint assigns the score to that > >> > node, but doesn't change scores assigned to other nodes. So if the node > >> > in question happens to be offline, the resource will be started on any > >> > other node. > > > > AFAIU, this behavior is expected when you set up your cluster with the > > Opt-In strategy: > > > > http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/#_deciding_which_nodes_a_resource_can_run_on > > > > No, this is the behavior of an Opt-Out cluster. So it seems you are > under the same misconception as I was. :) Sorry, my previous mail could be read in two different way...I meant: «set your cluster with the Opt-in strategy if you want this behavior». :) _______________________________________________ Users mailing list: [email protected] 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
