[DRBD-user] secondary not getting promoted to primary

[Mona Sinha]

Hi,

I am using DRBD with the following configuration:
DRBD Conf file is :
skip {
}
global {
usage-count no;
}
common {
syncer { rate 100M; }
}
resource r0 {
protocol C;
handlers {
outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
}
startup {
wfc-timeout 1;
degr-wfc-timeout 60; # 1 minute.
}
disk {
on-io-error detach;
fencing resource-only;
}
net {
timeout 100;
connect-int 15;
ping-int 15;
ping-timeout 80;
max-buffers 2048;
ko-count 0;
after-sb-0pri discard-older-primary;
after-sb-1pri discard-secondary;
after-sb-2pri call-pri-lost-after-sb;
rr-conflict disconnect;
}
}
 There are two servers in cluster. One primary(as1) and other secondary
server(as2). Now if I try to follow this sequence:

stop secondary (as2)-> stop primary (as1)-> start secondary
(as2)(expectation that it will get promoted to primary)

It was found that there were some issues and the secondary server(as2)
could not be promoted as drbd stated that its state is not updated. Its
state was either inconsistent/outdated.
Can anyone please explain why its state was not updated?
During that time, there was no any pending sync operation.

Regards,
Mona
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20200311/6946a70c/attachment.htm>