[Pacemaker] Failing back a multi-state resource eg. DRBD
holger.teutsch at web.de
Fri Mar 11 08:45:07 EST 2011
On Mon, 2011-03-07 at 14:21 +0100, Dejan Muhamedagic wrote:
> On Fri, Mar 04, 2011 at 09:12:46AM -0500, David McCurley wrote:
> > Are you wanting to move all the resources back or just that one resource?
> > I'm still learning, but one simple way I move all resources back from nodeb to nodea is like this:
> > # on nodeb
> > sudo crm node standby
> > # now services migrate to nodea
> > # still on nodeb
> > sudo crm node online
> > This may be a naive way to do it but it works for now :)
> Yes, that would work. Though that would also make all other
> resources move from the standby node.
> > There is also a "crm resource migrate" to migrate individual resources. For that, see here:
> resource migrate has no option to move ms resources, i.e. to make
> another node the master.
> What would work right now is to create a temporary location
> location tmp1 ms-drbd0 \
> rule $id="tmp1-rule" $role="Master" inf: #uname eq nodea
> Then, once the drbd got promoted on nodea, just remove the
> crm configure delete tmp1
> Obviously, we'd need to make some improvements here. "resource
> migrate" uses crm_resource to insert the location constraint,
> perhaps we should update it to also accept the role parameter.
> Can you please make an enhancement bugzilla report so that this
> doesn't get lost.
it seems that the original author did not file the bug.
I entered it as
More information about the Pacemaker