<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hello everyone,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’ve been reading a lot lately about using Corosync/Openais
in combination with Pacemaker: SuSe Linux documentation, Pacemaker & Linux-ha
website, interesting blogs, mailinglists, etc. As I’m particularly
interested in how well two node clusters (located within the same server room) are
handled, I was a bit confused by the fact that quorum disks/ quorum servers are
(not yet?) supported/used. Some suggested to add a third node which is not
actively participating (e.g. only running corosync.... or with hearbeat but in
standby mode). That might be a solution but doesn’t “feel”
right, especially if you consider multiple two-node clusters... that would
require a lot of extra “quorum only nodes”. Somehow SBD (storage
based death) in combination with a hardware watchdog timer seemed to also
provide a solution: run it on top of iSCSI storage and you end up with a
fencing device and some sort of “network based quorum” as
tiebreaker. If one node loses network connectivity, sbd + watchdog will make
sure it’s being fenced.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’d love to hear your ideas about 2 node cluster
setups. What is the best way to do it? Any chance we’ll get quorum disks/
quorum servers in the (near) future?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>In addition, say you’re not using sbd but an IPMI
based fencing solution. You lose network connectivity on one of the nodes (I
know, they’re redundant but still...sh*t happens ;) Does Pacemaker know
which of both nodes lost network connectivity? E.g.: node 1 runs Oracle
database, node 2 nothing. Node 2 loses network connectivity (e.g. both NICs without
signal because unplugged by an errant technician ;) )... => split brain
situation occurs, but who’ll be fenced? The one with Oracle running ?? I
really hope not... cause in this case, the cluster can “see” there’s
no signal on the NICs of node2. Would be interesting to know more about how
Pacemaker/corosync makes such kind of decisions... how to choose which one will
be fenced in case of split brain. Is it randomly chosen? Is it the DC which
decides? Based on NIC state? I did some quick testing with 2 VMs and at first,
it looks like Pacemaker/corosync always fences the correct node, or: the node where
I unplugged the “virtual” cable. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’m curious!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks a lot!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Best regards,<o:p></o:p></p>
<p class=MsoNormal>Dirk<o:p></o:p></p>
</div>
</body>
</html>