Testing some different scenarios, and after bringing a node back online, none of the resources move to it unless they are restarted. However default-resource-stickiness is set to 0, so they should be able to move around freely.
# pcs status Cluster name: docker Last updated: Wed Jun 4 06:09:26 2014 Last change: Wed Jun 4 06:08:40 2014 via cibadmin on i-093f1f55 Stack: corosync Current DC: i-083f1f54 (3) - partition with quorum Version: 1.1.11-1.fc20-9d39a6b 3 Nodes configured 8 Resources configured Online: [ i-053f1f59 i-083f1f54 i-093f1f55 ] Full list of resources: dummy2 (ocf::pacemaker:Dummy): Started i-083f1f54 Clone Set: dummy1-clone [dummy1] (unique) dummy1:0 (ocf::pacemaker:Dummy): Started i-083f1f54 dummy1:1 (ocf::pacemaker:Dummy): Started i-093f1f55 dummy1:2 (ocf::pacemaker:Dummy): Started i-093f1f55 dummy1:3 (ocf::pacemaker:Dummy): Started i-083f1f54 dummy1:4 (ocf::pacemaker:Dummy): Started i-093f1f55 # pcs resource show --all Resource: dummy2 (class=ocf provider=pacemaker type=Dummy) Clone: dummy1-clone Meta Attrs: clone-max=5 clone-node-max=5 globally-unique=true Resource: dummy1 (class=ocf provider=pacemaker type=Dummy) # pcs property show --all | grep default-resource-stickiness default-resource-stickiness: 0 Notice how i-053f1f59 isn't running anything. I feel like I'm missing something obvious, but it escapes me. Thanks -Patrick
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org