<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/25/2017 01:42 PM, Dr. Volker
Jaenisch wrote:<br>
</div>
<blockquote
cite="mid:dbb0ae53-d5d5-b0d4-c595-37fa0770ae87@inqbus.de"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
[ ... ]<br>
But this is not what we like to happen in this case. In the case
of communication breakdown of DRBD but still a connection between
the corosync nodes, we would like the cluster nodes :<br>
1) to remain in their state,<br>
2) prevent DRBD from failover,<br>
3) Indicate that the DRBD connection is broken<br>
</blockquote>
Starting with drbd-utils 8.9.10, the package contains another
utility named "drbdmon" that shows the current status of<br>
resources in a very compressed style, highlighting problems such as
disconnected resources on separate lines.<br>
<blockquote
cite="mid:dbb0ae53-d5d5-b0d4-c595-37fa0770ae87@inqbus.de"
type="cite"> 4) wait for reestablishing of the connection and
resync the drbd after,<br>
</blockquote>
That's what DRBD's default behavior is already. If something else
happens, then the cause is probably somewhat more complex than just
a temporarily lost network connection.<br>
<blockquote
cite="mid:dbb0ae53-d5d5-b0d4-c595-37fa0770ae87@inqbus.de"
type="cite"> 5) allow failover again.<br>
<br>
[...]<br>
<br>
Cheers,<br>
<br>
Volker<br>
<br>
</blockquote>
-- <br>
Robert Altnoeder<br>
+43 1 817 82 92 0<br>
<a class="moz-txt-link-abbreviated" href="mailto:robert.altnoeder@linbit.com">robert.altnoeder@linbit.com</a><br>
<br>
LINBIT | Keeping The Digital World Running<br>
DRBD - Corosync - Pacemaker<br>
f / t / in / g+<br>
<br>
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.<br>
</body>
</html>