On 06/26/2014 04:14 PM, emmanuel segura wrote:
> why you doesn't you a group for fs ip and apache resource?
>
> example:
>
> colocation fs_colocation inf: mygroup ms_drbd:Master
> order fs_order inf: ms_drbd:promote mygroup:start
>
> 2014-06-26 15:27 GMT+02:00 Xzarth
I have a pacemaker cluster with following config:
crm(live)configure# show
node node1
node node2
primitive ClusterIP ocf:heartbeat:IPaddr2 \
params ip="192.168.56.111" cidr_netmask="32" nic="eth1"
iflabel="1" \
op monitor interval="30s"
primitive apa
Hi,
I updated from pacemaker 1.0.9 to 1.1.7
After the update, cluster behaves differently than before. I have a
resource with migration-treshold="1", once that resource fails
everything used to migrate to another node (what i would expect).
After the upgrade, once that resource fails, cluster stop
