In my case: I have non symmetric-cluster (crm configure property
symmetric-cluster="false"). It's mean that all resources must have start
location value. So I have 100 and 10 for start. But in your case: you have
the same in normal situation. That's why your resource stick to the node.
I have res
Viacheslav Biriukov writes:
> Hello!
>
> Does ping resource and stickiness may work together?
> For example I have next resources:
>
> primitive P_INTRANET ocf:pacemaker:ping \
> params host_list="192.168.56.1 192.168.56.100" multiplier="111"
name="ping_intranet" \
> op monitor int
Hello!
Does ping resource and stickiness may work together?
For example I have next resources:
primitive P_INTRANET ocf:pacemaker:ping \
params host_list="192.168.56.1 192.168.56.100" multiplier="111"
name="ping_intranet" \
op monitor interval="5s" timeout="20s"
clone CL_INTRANET P_INTRANET \
me
