[Pacemaker] Unexpected resource restarts after putting a node in standby mode

Florian Haas florian.haas at linbit.com
Fri Jul 10 13:11:03 EDT 2009

On 07/10/2009 02:26 PM, Lars Marowsky-Bree wrote:
> On 2009-07-06T08:00:38, Florian Haas <florian.haas at linbit.com> wrote:
>> ms ms_drbd_iscsivg01 res_drbd_iscsivg01 \
>> 	meta clone-max="2" clone-node-max="1" master-max="1"
>> master-node-max="1" target-role="Started" notify="true"
>> ms ms_drbd_iscsivg02 res_drbd_iscsivg02 \
>> 	meta master-max="1" clone-max="2" clone-node-max="1"
>> master-node-max="1" notify="true" target-role="Started"
>> clone cl_tgtd res_tgtd \
>> 	meta target-role="Started"
> Try adding interleave="true" to the clone's meta-attributes. It might
> also be required for the ms ones, but I'm not sure about that.

Nope, doesn't do it. Tried adding interleave="true" to just the clone
first, then the clone and the ms resources, but I'm still getting
unexpected resource restarts.

Time to do as Dejan suggested and file a bug on this one, I guess.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20090710/837b9425/attachment-0003.sig>

More information about the Pacemaker mailing list