<div dir="ltr">Thanks for clarifying this ...<div><br></div><div>Regards,</div><div>Yannis</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 3, 2017 at 12:30 PM, Roland Kammerer <span dir="ltr"><<a href="mailto:roland.kammerer@linbit.com" target="_blank">roland.kammerer@linbit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Oct 03, 2017 at 12:05:50PM +0100, Yannis Milios wrote:<br>
> I think you have to use 'drbdmanage reelect' command to reelect a new<br>
> leader first.<br>
><br>
> man drbdmanage-reelect<br>
<br>
</span>In general that is a bad idea, and I regret that I exposed it as a<br>
subcommand and did not hide it behind a<br>
"--no-you-dont-want-that-<wbr>unless-you-are-rck" where it then sill asks you<br>
to prove the Riemann hypothesis before continuing...<br>
<span class=""><br>
> On Mon, Oct 2, 2017 at 2:12 PM, Jason Fitzpatrick <<a href="mailto:jayfitzpatrick@gmail.com">jayfitzpatrick@gmail.com</a>><br>
> wrote:<br>
><br>
> > Hi all<br>
> ><br>
> > I am trying to get my head around the quorum-control features within<br>
> > drbdmanage,<br>
> ><br>
> > I have deliberately crashed my cluster, and spun up one node, and as<br>
> > expected I am unable to get drbdmanage to start due to the lack of<br>
> > quorum,,<br>
> ><br>
> > I was under the impression that I should have been able to override<br>
> > the quorum state and get the drbdmanaged process online using DBUS /<br>
> > manually calling the service, but am drawing a blank..<br>
> ><br>
> > for the sake of this example it is a 2 node cluster node1 is online<br>
> > and node2 is still powered off,<br>
> ><br>
> > [root@node1]# drbdmanage quorum-control --override ignore node2<br>
> > Modifying quorum state of node 'node2':<br>
> > Waiting for server: ...............<br>
> > Error: Startup not successful (no quorum? not *both* nodes up in a 2<br>
> > node cluster?)<br>
> > Error: Startup not successful (no quorum? not *both* nodes up in a 2<br>
> > node cluster?)<br>
> ><br>
> > Any advice?<br>
<br>
</span>Bring back the second node. In two node clusters that is the only clean<br>
way to bring back the cluster. If you want quorum, get >=3 nodes.<br>
Period. In two node clusters both have to be up. "reelect" is a last<br>
resort command for the absolute worst case to bring up a 2 node cluster<br>
where only one node survived and the other one is gone beyond repair.<br>
"reelect" with a forced win alters internal state to make that possible.<br>
It does not revert that internal state if, for whatever reason the<br>
second node then shows up again. You would have to restart the "reelect"<br>
node to get it then in a sane internal state again.<br>
<br>
tl;tr: If you want quorum: >=3 nodes. Don't use "reelect" to force wins.<br>
<br>
Regards, rck<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">http://lists.linbit.com/<wbr>mailman/listinfo/drbd-user</a><br>
</div></div></blockquote></div><br></div>