{"action":"created","issue":{"url":"https://api.github.com/repos/akkadotnet/akka.net/issues/1359","labels_url":"https://api.github.com/repos/akkadotnet/akka.net/issues/1359/labels{/name}","comments_url":"https://api.github.com/repos/akkadotnet/akka.net/issues/1359/comments","events_url":"https://api.github.com/repos/akkadotnet/akka.net/issues/1359/events","html_url":"https://github.com/akkadotnet/akka.net/issues/1359","id":109840943,"number":1359,"title":"Akka.Cluster problem on seed node rejoin","user":{"login":"Horusiath","id":679705,"avatar_url":"https://avatars.githubusercontent.com/u/679705?v=3","gravatar_id":"","url":"https://api.github.com/users/Horusiath","html_url":"https://github.com/Horusiath","followers_url":"https://api.github.com/users/Horusiath/followers","following_url":"https://api.github.com/users/Horusiath/following{/other_user}","gists_url":"https://api.github.com/users/Horusiath/gists{/gist_id}","starred_url":"https://api.github.com/users/Horusiath/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Horusiath/subscriptions","organizations_url":"https://api.github.com/users/Horusiath/orgs","repos_url":"https://api.github.com/users/Horusiath/repos","events_url":"https://api.github.com/users/Horusiath/events{/privacy}","received_events_url":"https://api.github.com/users/Horusiath/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/akkadotnet/akka.net/labels/akka-cluster","name":"akka-cluster","color":"c7def8"},{"url":"https://api.github.com/repos/akkadotnet/akka.net/labels/akka-remote","name":"akka-remote","color":"c7def8"},{"url":"https://api.github.com/repos/akkadotnet/akka.net/labels/potential%20bug","name":"potential bug","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-10-05T16:54:50Z","updated_at":"2015-10-06T09:36:18Z","closed_at":null,"body":"From @christiansparre:\r\n\r\n> We have 4 members, two of them are seed nodes. When shutting down the leader, the remaining seed node is elected leader. If we shutdown that node, one of the remaining two non-seed nodes are elected leader. This is what we expected. However if we start one of the original seed nodes again we see the following error on the remaining two non-seed nodes. And that node is not \"allowed\" to join and remains out in the cold. \r\n\r\nThis is the error: \"Association to [akka.tcp://clustertest@127.0.0.1:7000] having UID [443331660] is irrecoverably failed. UID is now quarantined and all messages to this UID will be delivered to dead letters. Remote actorsystem must be restarted to recover from this situation.\""},"comment":{"url":"https://api.github.com/repos/akkadotnet/akka.net/issues/comments/145798382","html_url":"https://github.com/akkadotnet/akka.net/issues/1359#issuecomment-145798382","issue_url":"https://api.github.com/repos/akkadotnet/akka.net/issues/1359","id":145798382,"user":{"login":"rogeralsing","id":647031,"avatar_url":"https://avatars.githubusercontent.com/u/647031?v=3","gravatar_id":"","url":"https://api.github.com/users/rogeralsing","html_url":"https://github.com/rogeralsing","followers_url":"https://api.github.com/users/rogeralsing/followers","following_url":"https://api.github.com/users/rogeralsing/following{/other_user}","gists_url":"https://api.github.com/users/rogeralsing/gists{/gist_id}","starred_url":"https://api.github.com/users/rogeralsing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rogeralsing/subscriptions","organizations_url":"https://api.github.com/users/rogeralsing/orgs","repos_url":"https://api.github.com/users/rogeralsing/repos","events_url":"https://api.github.com/users/rogeralsing/events{/privacy}","received_events_url":"https://api.github.com/users/rogeralsing/received_events","type":"User","site_admin":false},"created_at":"2015-10-06T09:36:18Z","updated_at":"2015-10-06T09:36:18Z","body":"I'm verifying this against the Scala bits.\r\nIn Scala, when **auto down is set to off**, the restarted seed node is accepted back into the cluster.\r\nWhile if **auto down is set to on**, the restarted seed node is **not** accepted back into the cluster.\r\n\r\nThis was also verified by Konrad/Typesafe\r\n\r\n>rogeralsing 11:32:in a cluster scenario where there are some active worker nodes and all seed nodes goes down, and autodown is set to off, what is the expected behavior when a seednode comes back online? should the preexisting workers be able to re-establish a connection and let the seed back in.. or is the intended behavior that we see two different clusters , one with just the restarted seed and one with all the workers?\r\n\r\n>ktoso 11:33:   @rogeralsing no partition should happen then. Since the node was never declared \"down\".\r\n\r\n>rogeralsing 11:34: @ktoso and if auto down is on, then there should be a partition, right?\r\n\r\n>ktoso 11:34: yeah"}}