<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On 10 Apr 2017 7:42 am, "Marco Certelli" <<a href="mailto:marco_certelli@yahoo.it">marco_certelli@yahoo.it</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:verdana,helvetica,sans-serif;font-size:16px"><div id="m_-5174399953879955863yui_3_16_0_ym19_1_1491770995496_10767">Hello. Thanks for the answer.</div><div id="m_-5174399953879955863yui_3_16_0_ym19_1_1491770995496_10834">Maybe I was not clear: I do not want the authomatic poweroff of the server.</div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Why do you have problem with this? The server is already powering off right?</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:verdana,helvetica,sans-serif;font-size:16px"><div id="m_-5174399953879955863yui_3_16_0_ym19_1_1491770995496_11144">My problem is that if I manually poweroff the primary node (i.e. the server with DRBD primary mounted on), the secondary does not become primary (promote) anymore!</div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto"></div><div dir="auto">From the docs:</div><div dir="auto"><span style="color:rgb(39,41,46);font-family:"open sans";font-size:14px;background-color:rgb(255,255,255)">Thus, if the DRBD replication link becomes disconnected, the </span><code style="font-family:monaco,menlo,consolas,"courier new",monospace;font-size:12.6px;padding:0px 0.3em;color:rgb(50,50,50);background-color:rgb(240,240,255);border-radius:0px;font-weight:bold">crm-fence-peer.sh</code><span style="color:rgb(39,41,46);font-family:"open sans";font-size:14px;background-color:rgb(255,255,255)"> script contacts the cluster manager, determines the Pacemaker Master/Slave resource associated with this DRBD resource, and ensures that the Master/Slave resource no longer gets promoted on any node other than the currently active one. Conversely, when the connection is re-established and DRBD completes its synchronization process, then that constraint is removed and the cluster manager is free to promote the resource on any node again.</span><br></div><div dir="auto"><span style="color:rgb(39,41,46);font-family:"open sans";font-size:14px;background-color:rgb(255,255,255)"><br></span></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:verdana,helvetica,sans-serif;font-size:16px"><div id="m_-5174399953879955863yui_3_16_0_ym19_1_1491770995496_11149">It seems that the primary, just before powering off, fences the other node and precludes it to become primary. </div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">No, see above it is working as designed.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:verdana,helvetica,sans-serif;font-size:16px"><div id="m_-5174399953879955863yui_3_16_0_ym19_1_1491770995496_11149">This not the expected logic in a two nodes cluster...</div><div id="m_-5174399953879955863yui_3_16_0_ym19_1_1491770995496_10765">Is there a way?</div><div class="elided-text"><div id="m_-5174399953879955863yui_3_16_0_ym19_1_1491770995496_10701"><span></span></div> <div class="m_-5174399953879955863qtdSeparateBR"><br><br></div><div class="m_-5174399953879955863yahoo_quoted" style="display:block"> <div style="font-family:verdana,helvetica,sans-serif;font-size:16px"> <div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"> <div dir="ltr"><font size="2" face="Arial"> Il Domenica 9 Aprile 2017 22:48, Digimer <<a href="mailto:lists@alteeve.ca">lists@alteeve.ca</a>> ha scritto:<br></font></div> <br><br> <div class="m_-5174399953879955863y_msg_container"><div dir="ltr">On 09/04/17 03:05 PM, Marco Certelli wrote:<br clear="none">> Hello,<br clear="none">> <br clear="none">> very simple question for DRBD experts. I'm configuring Pacemaker (2<br clear="none">> nodes Active/Standby)+DRBD shared disk with the following config:<br clear="none">> <br clear="none">> ...<br clear="none">> disk {<br clear="none">> fencing resource-only;<br clear="none"><br clear="none">This should be 'resource-and-stonith;'<div class="m_-5174399953879955863yqt3228314602" id="m_-5174399953879955863yqtfd52297"><br clear="none"><br clear="none">> }<br clear="none">> handlers {<br clear="none">> fence-peer "/usr/lib/drbd/crm-fence-peer.<wbr>sh";<br clear="none">> after-resync-target "/usr/lib/drbd/crm-unfence-<wbr>peer.sh";<br clear="none">> }<br clear="none">> ...<br clear="none">> <br clear="none">> It happen that if I poweroff the Active server (the one with DRBD<br clear="none">> Primary mounted on), the backup cannot promote and mount the DRBD<br clear="none">> anymore. This is not what I would like to happen and this problem does<br clear="none">> not occur if I remove the above fencing configuration (fencing,<br clear="none">> fence-peer and after-resync-target commands).<br clear="none">> <br clear="none">> My only objective is to prevent promoting of a disk that is under<br clear="none">> resynch. Is there a solution? I was thinking to the following configuration:<br clear="none">> <br clear="none">> ...<br clear="none">> disk {<br clear="none">> fencing resource-only;<br clear="none">> }<br clear="none">> handlers {<br clear="none">> before-resync-target "/usr/lib/drbd/crm-fence-peer.<wbr>sh";<br clear="none">> after-resync-target "/usr/lib/drbd/crm-unfence-<wbr>peer.sh";<br clear="none">> }<br clear="none">> ...<br clear="none">> <br clear="none">> Do you think it may work, without other negative effects?<br clear="none">> <br clear="none">> Thanks, Marco.</div><br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> ______________________________<wbr>_________________<br clear="none">> drbd-user mailing list<br clear="none">> <a shape="rect">drbd-user@lists.linbit.com</a><br clear="none">> <a shape="rect">http://lists.linbit.com/<wbr>mailman/listinfo/drbd-user</a><br clear="none">> <br clear="none"><br clear="none"><br clear="none">-- <br clear="none">Digimer<br clear="none">Papers and Projects: <a shape="rect">https://alteeve.com/w/</a><br clear="none">"I am, somehow, less interested in the weight and convolutions of<br clear="none">Einstein’s brain than in the near certainty that people of equal talent<br clear="none">have lived and died in cotton fields and sweatshops." - Stephen Jay Gould<div class="m_-5174399953879955863yqt3228314602" id="m_-5174399953879955863yqtfd20719"><br clear="none"></div></div><br><br></div> </div> </div> </div></div></div></div><br>______________________________<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/">http://lists.linbit.com/</a><wbr>mailman/listinfo/drbd-user<br>
<br></blockquote></div><br></div></div></div>