<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/24/2017 05:32 PM, Tomer Azran
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ED2704A50931F4F2.cf092478-6729-42dd-88d8-8651b7766e1f@mail.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
So your suggestion is to use sbd with or without qdevice? What
is the point of having a qdevice in two node cluster if it
doesn't help in this situation?<br>
</div>
</blockquote>
<br>
If you have a qdevice setup that is already working (meaning in
terms of that one<br>
of your nodes is quorate and the other not if they are split) I
would use that.<br>
And if you use sbd with just a watchdog (no shared disk) - should be
supported in <br>
Centos 7.3 (you said you are there somewhere down below iirc) - it
would be<br>
assured that the node that is not quorate goes down reliably and
that the other<br>
node is assuming it to be down after a timeout you configured using
cluster<br>
property stonith-watchdog-timeout.<br>
<br>
<blockquote type="cite"
cite="mid:ED2704A50931F4F2.cf092478-6729-42dd-88d8-8651b7766e1f@mail.outlook.com">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
From: Klaus Wenninger<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
Sent: Monday, July 24, 18:28<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
Subject: Re: [ClusterLabs] Two nodes cluster issue<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
To: Cluster Labs - All topics related to open-source clustering
welcomed, Tomer Azran<br>
<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
On 07/24/2017 05:15 PM, Tomer Azran wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
I still don't understand why the qdevice concept doesn't help
on this situation. Since the master node is down, I would
expect the quorum to declare it as dead.<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
Why doesn't it happens?<br>
</div>
</blockquote>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
That is not how quorum works. It just limits the decision-making
to the quorate subset of the cluster.<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
Still the unknown nodes are not sure to be down.<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
That is why I suggested to have quorum-based watchdog-fencing
with sbd.<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
That would assure that within a certain time all nodes of the
non-quorate part<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
of the cluster are down.<br>
<br>
</div>
<blockquote type="cite">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
<br>
<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
On Mon, Jul 24, 2017 at 4:15 PM +0300, "Dmitri Maziuk" <<a
href="mailto:dmitri.maziuk@gmail.com" moz-do-not-send="true">dmitri.maziuk@gmail.com</a>>
wrote:<br>
<br>
</div>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
On 2017-07-24 07:51, Tomer Azran wrote: > We don't have
the ability to use it. > Is that the only solution? No,
but I'd recommend thinking about it first. Are you sure you
will care about your cluster working when your server room
is on fire? 'Cause unless you have halon suppression, your
server room is a complete write-off anyway. (Think water
from sprinklers hitting rich chunky volts in the servers.)
Dima _______________________________________________ Users
mailing list:
<a href="mailto:Users@clusterlabs.org"
moz-do-not-send="true">Users@clusterlabs.org</a> <a
href="http://lists.clusterlabs.org/mailman/listinfo/users"
moz-do-not-send="true">
http://lists.clusterlabs.org/mailman/</a><a
href="http://lists.clusterlabs.org/mailman/listinfo/users"
moz-do-not-send="true">listinfo</a><a
href="http://lists.clusterlabs.org/mailman/listinfo/users"
moz-do-not-send="true">/users</a> Project Home:
<a href="http://www.clusterlabs.org" moz-do-not-send="true">http://www.clusterlabs.org</a>
Getting started:
<a
href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf"
moz-do-not-send="true">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs:
<a href="http://bugs.clusterlabs.org" moz-do-not-send="true">http://bugs.clusterlabs.org</a>
<br>
</div>
</blockquote>
</blockquote>
<blockquote type="cite">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
_______________________________________________ Users mailing
list: <a href="mailto:Users@clusterlabs.org"
moz-do-not-send="true">
Users@clusterlabs.org</a> <a
href="http://lists.clusterlabs.org/mailman/listinfo/users"
moz-do-not-send="true">
http://lists.clusterlabs.org/mailman/</a><a
href="http://lists.clusterlabs.org/mailman/listinfo/users"
moz-do-not-send="true">listinfo</a><a
href="http://lists.clusterlabs.org/mailman/listinfo/users"
moz-do-not-send="true">/users</a> Project Home:
<a href="http://www.clusterlabs.org" moz-do-not-send="true">http://www.clusterlabs.org</a>
Getting started:
<a
href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf"
moz-do-not-send="true">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs:
<a href="http://bugs.clusterlabs.org" moz-do-not-send="true">http://bugs.clusterlabs.org</a>
<br>
</div>
</blockquote>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black;
background-color: white;">
<br>
</div>
<br>
</blockquote>
</body>
</html>