Re: [Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby - possible solution?

On , Andrew Beekhof wrote: On 19 May 2014, at 4:17 pm, Andrew Beekhof wrote: On 16 May 2014, at 3:41 am, Ian wrote: Doing some experiments and Reading TFM, I found this: 5.2.2. Advisory Ordering When the kind=Optional option is specified for an order constraint, the constraint is

Re: [Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby - possible solution?

server with vm_storage_core-clone (INFINITY) (id:colocation-res_vm_nfs_server-vm_storage_core-clone-INFINITY) Ian. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http:

Re: [Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby

David Vossel wrote: does setting resource-stickiness help? http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#s-resource-options Thanks for the suggestion. Applied resource-stickiness=100 to the vm resource, doesn't seem to have any effect (same beh

[Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby

sv07 crmd[3158]: notice: process_lrm_event: LRM operation res_drbd_vm1_notify_0 (call=1539, rc=0, cib-update=0, confirmed=true) ok Thanks for looking, Ian. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.o