[Pacemaker] Odd behaviour produced by resource migration

Michael Schwartzkopff misch at clusterbau.com
Wed Feb 2 10:31:14 EST 2011


On Wednesday 02 February 2011 15:37:48 Dominik Dingel wrote:
> Hello there,
> 
> I'm currently setting up a two node cluster with:
> - dual primary drbd
> - dlm
> - o2cb
> - ocfs2 filesystem
> - openvz container
> to be a active-passiv cluster solution.
> 
> Stonith is configured to use IPMI and meatware as fallback, so even in
> case where a server would be removed, the remaining node could be powered
> on with little effort.
> So now I'm testing all scenarios of the cluster. The migration of the
> container is one thing which does not work as I would like it to work.
> 
> After a fresh power-on of both nodes and so the cluster came online,
> resulting in this output:
> http://pastebin.com/4Hdz5bjy
> 
> After issuing then the line:
> > crm resource migrate resVZ
> 
> to move the container from node2 to node1 all services on node2 will be
> stopped as msDRBD on node2 is demoted.
> http://pastebin.com/yxgBkYTf
> I don't understand why the resource (drbd) is demoted in the first place
> and if there is a way to prevent this.
> 
> 
> Thanks a lot in advance!
> 
> Best Regards
> 
> Dominik


HI,

If you have a active/passive cluster you do not need the dlm, o2cb, ocfs2 
stuff. Just use a plain ext3.

-- 
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110202/d8c6ebb6/attachment-0004.sig>


More information about the Pacemaker mailing list