<html><head></head><body bgcolor="#FFFFFF"><div>I afraid that in same cases dying VM won't send anything. Additional technique that might help in this situation is a watchdog process, but it bring another level of abstraction/complexity.</div><div><br></div><div>In our project we also need to monitor distributed systems and we will implement watchdogs.<br><br>Sent from my iPad</div><div><br>On 15.09.2012, at 10:21, Torben Hoffmann <<a href="mailto:torben.lehoff@gmail.com">torben.lehoff@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
Hi Roberto,<br>
<br>
Try contacting Laura Castro from Uni of Coruña who presented at the
Erlang Workshop 2012 yesterday regarding handling of netsplits and
node crashes.<br>
Their team had to go through some investigations before they got the
resilience they had promised the customer! <br>
<br>
The big question for you will actually be what to do when the layers
thinks that the other node is down - will you assume a net split and
buffer communication (if that is feasible for your application)? Or
will you assume node down and do a major clean-up?<br>
<br>
Cheers,<br>
___<br>
/orben<br>
<br>
<br>
<div class="moz-cite-prefix">On 2012-09-15 03:46, Roberto Ostinelli
wrote:<br>
</div>
<blockquote cite="mid:CAM5fRypo52mv86Qd+q0JMNK1tki56OxEhP-G5AUaW8n7CcZEqQ@mail.gmail.com" type="cite">hello Michael,
<div><br>
</div>
<div>you're assuming right (separate VM), I'm familiar with links
and monitors, thank you. However I doubt that any message is
sent from a dying process if the VM on which it runs actually
blows up. That was my point.</div>
<div><br>
</div>
<div>r.</div>
<div><br>
<br>
<div class="gmail_quote">On Fri, Sep 14, 2012 at 3:47 PM,
Michael Truog <span dir="ltr"><<a moz-do-not-send="true" href="mailto:mjtruog@gmail.com" target="_blank">mjtruog@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#ffffff" text="#000000"> Assuming you have the
2 layers in separate Erlang VMs. You can have the Erlang
VMs connected with distributed Erlang, and have the twin
processes monitoring each other. If you wanted a simple
process death if either died, you could consider using a
link instead of 2 monitors. However, that seems like the
simplest solution, to avoid unnecessary complexity. You
might find strangeness if you start not using the default
net tick time (i.e., with a process link inbetween nodes),
with distributed Erlang, but you probably know it is best
to not play with that.
<div>
<div class="h5"><br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/torbenhoffmann">http://www.linkedin.com/in/torbenhoffmann</a></pre>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>erlang-questions mailing list</span><br><span><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a></span><br><span><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a></span><br></div></blockquote></body></html>