[Pacemaker] Drbd primary never on SyncTarget

Johan Verrept Johan.Verrept at able.be
Tue Sep 8 09:53:47 EDT 2009


On Tue, 2009-09-08 at 15:04 +0200, Florian Haas wrote:

> The question is moot in this case, though, as I already mentioned: all
> of this is handled via master preferences which the ocf:linbit:drbd RA
> updates automatically.

Yes. This works nicely with the new version. One remark I have is that
it is uncomfortable to work with if you have other (less important)
reasons to move the master: the left over "priority space" to work with
is rather small. You have to use values totalling less than 90 or you
will overrule the RA. If you have multiple considerations (multiple
network connections for example), you run out of space quickly.

> >> In function drbd_get_status I patched the line:
> >>
> >> DRBD_CSTATE=$(do_drbdadm cstate $RESOURCE)
> >>
> >> to
> >>
> >> DRBD_CSTATE=$(do_drbdadm cstate $RESOURCE | cut -d ' ' -f 1)
> >>
> >> because the cstate command returns extra output
> 
> Which extra output?

It only appeared when drbd was syncing and it seems to have disappeared
after upgrading drbd (from 8.3.0 to 8.3.2). It was a line that gave
information about the sync progress.

> > OK. Florian: Can you please comment on this too.
> 
> Bottom line: even though the ocf:linbit:drbd RA is officially still in
> beta, it's probably way superior to the ocf:heartbeat:drbd one.

It is in my experience.

Thanks for the feedback.

  Johan





More information about the Pacemaker mailing list