Hi all,

I was running a cluster of four nodes, one client node and three worker 
nodes in my testing.  

1) After which, a cluster.down(..) was issued to the client node.
2) The client node listens on
      leaves cluster
      Does coordinated shutdown
The actorSytem is reset to null.
3) After which, the client node, upon receiving new requests, tries to 
reinitialize the actorSystem with the same port.

That's when I see one time I was testing that this message was shown and 
kept showing indefinitely.
New incarnation of existing member [Member(address = 
akka.tcp://abc@machineName:4504, status = Down)] is trying to join. 
Existing will be removed from the cluster and then new member will be 
allowed to join.

But there are also times in my testing that the client is able to connect 
back to the worker nodes and jobs get processed.

When I see this message, does it mean the leader node is not doing its job?

I see that there is a similar jira filed here:

We are using Akka 2.5.9.  

Could you advise if this is a known issue and if there is any workaround?


** New discussion forum: https://discuss.akka.io/ replacing akka-user 
google-group soon.
** This group will soon be put into read-only mode, and replaced by 
** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to