[Pacemaker] corosync stop and consequences

[Michael Schwartzkopff]

Am Mittwoch, 26. Juni 2013, 16:36:43 schrieb andreas graeper:
> hi and thanks.
> a primitive can be moved to another node. how can i move (change roles) of
> drbd:master to the other node ?

Switch off the other node.


> and will all the depending resources follow?

Depends on your constraints(order/collocation).


> then i can stop (and start again) corosync on passive node without problem
> (my tiny experience).

Yes.


> another question: i found a location-constraint (i think it was set by some
> of the handlers in drbd-config):
> 
> location drbd:master -INF #uname ne n1
> does this mean: drbd must not get promoted on node other than n1 ?!

Yes. See: Resource fencing in DRBD.


> i found this in a situation, when n2 had gone and drbd could not get
> promoted on n1, so all the other resources did not start.
> but the problem was not drbd, cause i could manually set it to primary.

Yes. because this location constraint is valid inside the cluster software. 
Not outside.

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

Tel: (0163) 172 50 98
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130626/896106e7/attachment.htm>