<div dir="ltr"><div><div>According to distributed app documentation:<br><br>If the node where the application is running goes down,
the application is restarted (after the specified timeout) at
the first node, specified by the <span class="">distributed</span> configuration
parameter, which is up and running. This is called a
<strong>failover</strong>.<br><br></div>In your case, your node did not go down but supervisor is stopped. I did a test in the past of the application fail over by disabling ethernet adapater on the master node.<br>
<br></div>-- baliga<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 25, 2013 at 11:28 AM, Phillips, Christopher <span dir="ltr"><<a href="mailto:Christopher.Phillips@turner.com" target="_blank">Christopher.Phillips@turner.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div>I have a release built around a distributed application. </div>
<div><br>
</div>
<div>If I spin two nodes up, things are configured properly such that if I attach and q() out of the node the application is actively running on, failover occurs, the application starts up on the other node.</div>
<div><br>
</div>
<div>What I'm finding is that in the same situation, if I kill the top level supervisor (either by directly sending it an exit message, or having a child fail enough times to pass the max restart threshold), I _don't_ fail over. I do, however, receive a node
down message on the other node. I'm wondering if this is intentional, a bug, or if I'm doing something wrong.</div>
</div>
<br>_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br></blockquote></div><br></div>