Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, May 28, 2009 at 09:10:48AM +0400, Maxim Vladimirsky wrote:
> Hi Everybody,
>
> We have been using DRBD 0.7.24 for very long time. But the time for upgrade
> has finally come. So DRBD 8.3.1 was installed and drbd.conf adjusted.
> However now DRBD behaves differently when primary node gets rebooted. When
> we were running DRBD 0.7.24 and the primary node went down the secondary one
> took over primary role, and when the faulty node got up it became secondary.
> Now when we are running DRBD 8.3.1 if primary node goes down the secondary
> one still takes over, but when the faulty node gets up, both nodes go in
> stand-alone mode breaking the cluster in pieces.
I am sure they do _log_ why they are going StandAlone.
Maybe you want to let us know?
> I guess that we made a mistake in our drbd.conf file. Could please someone
> advise where it is. Our configuration file is as follows:
My guess is that somehow your init script start/stop order got screwed up.
> global {
> usage-count no;
> }
> resource shared {
> protocol C;
> handlers {
> pri-on-incon-degr "echo '!DRBD! pri on incon-degr' | wall ; sleep 15
> ; halt -f";
> }
> startup {
> wfc-timeout 1;
> degr-wfc-timeout 1;
> outdated-wfc-timeout 1;
these are pretty short, basically disabled.
why?
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed