<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi,<br>I am too waiting for this. Could you please let me know in which version of Erlang/OTP, this will be included and approximately when that version can be released?<br>Thanks.<br><br>-
<br>Zulfiqer
<br><br><div>> Date: Wed, 19 Nov 2014 13:18:08 -0800<br>> From: raould@gmail.com<br>> To: erlang-questions@erlang.org<br>> Subject: Re: [erlang-questions] Distributed application and netsplit<br>> <br>> > The problem is, once the net split has been detected, how then to manually shutdown the unwanted application instance(s) in such a way that the distributed application failover continues to work from that point forward.<br>> ><br>> > The OP already has application-specific code which is able to detect that a net split / split brain scenario has occurred.<br>> ><br>> > Furthermore, the OP is “ok” writing application specific code to attempt to resolve the situation at that point.<br>> ><br>> > The question is, what is the “best” way to go about doing that?<br>> <br>> <br>> <br>> thanks.<br>> <br>> ok so it sounds like more clearly what we want is to know that OTP has<br>> been designed / will be updated to handle this at the level of it<br>> "going back to normal" at the OTP level, leaving the actual "sync up"<br>> part to the individual applications that use OTP.<br>> _______________________________________________<br>> erlang-questions mailing list<br>> erlang-questions@erlang.org<br>> http://erlang.org/mailman/listinfo/erlang-questions<br></div> </div></body>
</html>