[erlang-questions] unregistering a process during takeover

Nuku Ameyibor nayibor@REDACTED
Fri Jan 23 12:09:23 CET 2015

hi ulf ,
the takeover is working okay now  !!! .
config a is this

  [{distributed, [{m8ball,
                  [a@REDACTED, {b@REDACTED, c@REDACTED}]}]},
   {sync_nodes_mandatory, [b@REDACTED, c@REDACTED]},
   {sync_nodes_timeout, 30000}

i start each node with
bin\werl.exe -sname c -config

there are 3 nodes .their conf files are similar with sync_nodes_mandatory
being slightly different .

a small question .
the first round of  failover and takeover seems to work fine .
but after the first round (start node a,b,c  . kill a  b does failover
.kill b c does failover . restart a,b  a does takeover from c killing c
application on c .i restart shell on c  )

* after the first round when  i try to do a failover   onto b by killing a
it doesnt work .*
was wondering how come since the first round of failover take over worked
fine .

On Fri, Jan 23, 2015 at 6:35 AM, Ulf Wiger <ulf@REDACTED> wrote:

> On 23 Jan 2015, at 03:44, Nuku Ameyibor <nayibor@REDACTED> wrote:
> =INFO REPORT==== 23-Jan-2015::02:20:57 ===
> global: Name conflict terminating {m8ball_server,<2910.62.0>}
> This suggests that you’re connecting the nodes *after* starting your
> applications, so that the application processes have time to globally
> register themselves first. Global detects the name conflict when trying to
> merge the registries of the two nodes.
> You can for example use the ‘distributed’ option, described here:
> http://www.erlang.org/doc/apps/kernel/application.html#load-1
> and here:
> http://www.erlang.org/doc/man/kernel_app.html
> BR,
> Ulf W
> Ulf Wiger, Co-founder & Developer Advocate, Feuerlabs Inc.
> http://feuerlabs.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150123/9cbed728/attachment.htm>

More information about the erlang-questions mailing list