<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 11, 2015 at 3:08 AM, Digimer <span dir="ltr"><<a href="mailto:lists@alteeve.ca" target="_blank">lists@alteeve.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 10/12/15 09:27 AM, Fabrizio Zelaya wrote:<br>
> Thank you Lars and Adam for your recommendations.<br>
><br>
> I have ping-timeout set to 5 and it still happened.<br>
><br>
> Lars with this fencing idea. I have been contemplating this, however I<br>
> am rebuilding servers which are already in place, All the configuration<br>
> related to cman and drbd was literally copied and pasted from the old<br>
> servers.<br>
<br>
</span>You can hook DRBD into cman's fencing with the rhch_fence fence handler,<br>
which is included with DRBD. This assumes, of course, that you have<br>
cman's fencing configured properly.<br>
<span class=""><br>
> Is this concept of having dual-primary without fencing being a<br>
> mis-configuration something new?<br>
<br>
</span>No, but it is often overlooked.<br>
<span class=""><br>
> I ask this because as you would imagine by now, the old servers are<br>
> working with the exact same configuration and have no problems at all.<br>
> And while your idea makes perfect sense it would also make sense to have<br>
> the exact same problem on every version of drbd.<br>
<br>
</span>Fencing is like a seatbelt. You can drive for years never needing it,<br>
but when you do, it saves you from hitting the windshield.<br>
<br>
Fencing is 100% needed, and all the more so with dual-primary.<br></blockquote><div><br></div><div>So this practically excludes the DRBD usage in the public clouds like AWS, right? Here shutting down the peer's power supply is impossible and using the CLI has no guarantee that shutting down a peer VM will ever happen since has to be done via the network. Even if the VM's have multiple network interfaces provisioned for redundancy in different subnets they are still virtual and there is possibility they end up on the same physical interface on the hypervisor host which has failed (or it's switch), causing the split brain in the first place.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span class=""><br>
> There is a difference to be consider I guess. I am now installing this<br>
> servers using SL6 as you saw in my original email, the old servers are<br>
> working with Debian 6.0.7<br>
><br>
> The old servers are running drbd8-utils 2:8.3.7-2.1<br>
<br>
</span>--<br>
Digimer<br>
Papers and Projects: <a href="https://alteeve.ca/w/" rel="noreferrer" target="_blank">https://alteeve.ca/w/</a><br>
What if the cure for cancer is trapped in the mind of a person without<br>
access to education?<br>
<span class="">_______________________________________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
</span><a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</blockquote></div><br></div></div>