[Pacemaker] Failback problem with active/active cluster

[Robert Schumann]

Charles KOPROWSKI <cko at ...> writes:

> 
> Le 14/03/2011 09:43, Andrew Beekhof a écrit :
> > On Sat, Mar 12, 2011 at 9:53 AM, Pavel Levshin<pavel at ...>  wrote:
> >> 11.03.2011 16:27, Andrew Beekhof:
> >>>
> >>> On Fri, Mar 11, 2011 at 2:19 PM, Charles KOPROWSKI<cko at ...>
> >>>   wrote:
> >>>
> >>>> Is there any possibility to move back manualy a part of the ClusterIP
> >>>> resource (for example ClusterIP:1) to the other node ? Or is it just
> >>>> impossible with this version ?
> >>>
> >>> I _think_ its impossible - which is certainly not terribly useful
> >>> behavior.
> >>>
> >>
> >> What if you set clone-node-max=1 for the resource?
> >
> > Good point. Temporarily setting that should allow them to move back.

It works indeed:

1. crm configure
2. edit ClusterIP-clone
3. change clone-node-max from "2" to "1" and save
4. commit 
5. undo the change, commit again and service is started on both hosts (like 
before fail of one node)

@Pavel: good catch! 

The other clones like apache2, mysql, ocfs2, o2cb, dlm are coming up again as 
expected without interference (debian squeeze).

Nice work, guys - I really love it!

Best regards

Robert