<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 15 (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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Open Sans";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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
{mso-style-priority:99;
margin-top:0cm;
margin-right:0cm;
margin-bottom:9.75pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
code
{mso-style-priority:99;
font-family:Consolas;
color:#323232;
background:#F9F2F4;
font-weight:bold;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin-top:0cm;
margin-right:0cm;
margin-bottom:9.75pt;
margin-left:0cm;
background:whitesmoke;
word-break:break-all;
font-size:10.0pt;
font-family:Consolas;
color:#3D4045;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:#3D4045;
background:whitesmoke;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
margin-top:0cm;
margin-right:0cm;
margin-bottom:9.75pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></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="WordSection1">
<p class="MsoNormal">Bumping this thread.<o:p></o:p></p>
<p class="MsoNormal">Anybody knows if the behavior we see is a bug or a feature ??<o:p></o:p></p>
<p class="MsoNormal">To me it looks like a bug.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> /Per<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Per Sundström XP <br>
<b>Sent:</b> den 2 januari 2017 17:21<br>
<b>To:</b> 'drbd-user@lists.linbit.com' <drbd-user@lists.linbit.com><br>
<b>Subject:</b> v9.0: Node does not go into StandAlone on two primary split brain<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="SV">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="SV"><o:p> </o:p></span></p>
<p class="MsoNormal">We have been using DRBD V8 and are in the process of moving to V9.<o:p></o:p></p>
<p class="MsoNormal">To be exact: “version: 9.0.1-1 (api:2/proto:86-111) GIT-hash: 86e443973082570aeb651848db89e0c7b995c306 build by abuild)”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One difference that we see is that if configured with ”allow-two-primaries no” and when there is<o:p></o:p></p>
<p class="MsoNormal">a network disconnect that ends up in two [disconnected] primaries neither of them will go into “StandAlone” connection<o:p></o:p></p>
<p class="MsoNormal">state when the network is reconnected.<o:p></o:p></p>
<p class="MsoNormal">Instead both nodes stay in state “Connecting” and refuses to connect with the error: “Multiple primaries not allowed by config”<o:p></o:p></p>
<p class="MsoNormal">Due to this, the disk state is never compared and no split brain logic is triggered.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is this a bug or a feature with V9 ?<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:9.75pt;line-height:140%"><span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E">If this is expected behaviour, what is the new way of detecting that we have two primaries
?<o:p></o:p></span></p>
<p class="MsoNormal">One [hackish] workaround is to dynamically temporarily allow two primaries while in state “Connecting” but that does not feel right.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:9.75pt;line-height:140%"><span style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:9.75pt;line-height:140%"><span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E"> /Per<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The V9 documentation has this in it:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="line-height:140%">“<span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E">DRBD detects split brain at the time connectivity becomes available again and the peer nodes exchange the initial DRBD protocol
handshake. If DRBD detects that both nodes are (or were at some point, while disconnected) in the primary role, it immediately tears down the replication connection. The tell-tale sign of this is a message like the following appearing in the system log:<o:p></o:p></span></p>
<div style="border:solid #CCCCCC 1.0pt;padding:9.0pt 9.0pt 9.0pt 9.0pt">
<p class="MsoNormal" style="margin-bottom:9.75pt;background:whitesmoke;word-break:break-all">
<span lang="EN-GB" style="font-size:10.0pt;font-family:Consolas;color:#3D4045">Split-Brain detected, dropping connection!<o:p></o:p></span></p>
</div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal" style="margin-bottom:9.75pt;line-height:140%"><span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E">After split brain has been detected, one node will always have the resource in a
</span><b><span lang="EN-GB" style="font-size:9.5pt;line-height:140%;font-family:Consolas;color:#323232;background:#F9F2F4">StandAlone</span></b><span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E"> connection
state. The other might either also be in the </span><b><span lang="EN-GB" style="font-size:9.5pt;line-height:140%;font-family:Consolas;color:#323232;background:#F9F2F4">StandAlone</span></b><span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E">
state (if both nodes detected the split brain simultaneously), or in </span><b><span lang="EN-GB" style="font-size:9.5pt;line-height:140%;font-family:Consolas;color:#323232;background:#F9F2F4">WFConnection</span></b><span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E">
(if the peer tore down the connection before the other node had a chance to detect split brain).”<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:9.75pt;line-height:140%"><span lang="EN-GB" style="font-size:10.5pt;line-height:140%;font-family:"Open Sans",serif;color:#27292E"><o:p> </o:p></span></p>
</div>
</body>
</html>