<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=us-ascii">
<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;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1009061508;
mso-list-type:hybrid;
mso-list-template-ids:893932824 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal">With a Pacemaker 1.1.13/Corosync 2.3.5 cluster is it possible to define a relationship between two resources so that:<o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">B depends on A (a normal order constraint)<o:p></o:p></li></ol>
<p class="MsoNormal">AND<o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">If either fails, they both need to be stopped and restarted, in the order defined above (B stops, A stops, A starts, then B starts)<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the normal configuration, if A fails, then A and B will be restarted, because B depends on A. However, if B fails, only B is restarted because A does not depend on it. In most cases this is going to be fine, but we have a case where
in some situations B is failing precisely because A above it is having a failure (but we don’t know it yet).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The order attribute takes care of the ordering of the start/stop (along with adding colocation so they stay on the same node).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The problem I am trying to address is the case where the monitor for B fires first, and B is attempted to be restarted, but it won’t work until A is.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Case in point, LVM and Filesystem2 resources.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If LVM needs to be refreshed, the Filesystem above it stops working (e.g. I/O fails). However, Filesystem noticed a problem first, and LVM didn’t have a chance to see it also had a problem. Therefore, Filesystem will try to restart itself
until it exhausts its retries. At that point, a cleanup is required to get things going again, and LVM has to be manually restarted.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have a case where the LVM cache needs to be refreshed and the volumes reactivated to clear up a problem caused by paths going down and coming back up in a SAN causing the LVM VG to get in a compromised state, and the LVM problem causes
the Filesystem I/O to fail, and Filesystem notices first, monitor fails, it stops itself, and tries in vain to restart, because it will not until the LVM resource is restarted.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I made the monitor interval longer for Filesystem than LVM which makes LVM find the problem first, but that isn’t foolproof.<o:p></o:p></p>
<p class="MsoNormal">If it was a rule that if a Filesystem resource needs to be stopped and started that the LVM resource it depends on has to be restarted first, I should be able to avoid the problem entirely.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In essence, what I’m asking is if I can make two resource start and stop in a particular order, but also define that if one has to be started or stopped the other must as well (in my defined order).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #CCCCCC 1.0pt;padding:4.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:3.0pt;border:none;padding:0in"><b><span style="color:#444444">Greg Neitzert</span></b><span style="color:#444444"> | Lead Software Engineer |
</span><span style="color:#444444">RTC Software Engineering 2B - Middleware</span><span style="font-size:9.0pt;color:#444444">
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:3.0pt;border:none;padding:0in"><span style="font-size:9.0pt;color:#444444">Unisys Corp</span><span style="font-size:7.5pt;color:#999999"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>