On Tue, 2018-11-13 at 17:27 +0100, Valentin Vidic wrote: > On Tue, Nov 13, 2018 at 05:04:19PM +0100, Valentin Vidic wrote: > > Also it seems to require multicast, so better check for that too :) > > And while the CLUSTERIP resource seems to work for me in a test > cluster, the following clone definition: > > clone cip-clone cip \ > meta clone-max=2 clone-node-max=2 globally-unique=true > interleave=true target-role=Started > > allows for both clone instances to end up on the same node: > > Clone Set: cip-clone [cip] (unique) > cip:0 (ocf::heartbeat:IPaddr2): Started sid2 > cip:1 (ocf::heartbeat:IPaddr2): Started sid2 > > Is there a way to spread the resources other than setting > clone-node-max=1 for a while?
Clone instances have a default stickiness of 1 (instead of the usual 0) so that they aren't needlessly shuffled around nodes every transition. You can temporarily set an explicit stickiness of 0 to let them rebalance, then unset it to go back to the default. -- Ken Gaillot <[email protected]> _______________________________________________ Users mailing list: [email protected] https://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
