https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1459 controller <p>I observed that auto-down time function of cluster is not working properly.</p> <p>I created a 3 node cluster and configured 30s in my akka.conf. and I down 2 of my cluster node (shutdown the vm itself) and waited for nearly 45 mins, after that I restarted my vm (cluster) then I checked that the newly started 2 # vms (clusters) are getting formed a cluster with existing node. But as per the function, it should form a separate cluster (<a href="http://doc.akka.io/docs/akka/snapshot/scala/cluster-usage.html#Automatic_vs__Manual_Downing" class="external-link" target="_blank" rel="nofollow noopener">http://doc.akka.io/docs/akka/snapshot/scala/cluster-usage.html#Automatic_vs__Manual_Downing</a>)</p> <p>Herewith I am enclosing the karaf log of all 3 nodes</p> <p>I found this issue in SR3 Lithium image</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1459

cluster : 3node auto-down time of cluster is not working properly

Bug Resolved Cannot Reproduce Unassigned Anpukarasi Muthukumaran Thu, 10 Dec 2015 12:22:10 +0000 Thu, 19 Oct 2017 21:26:55 +0000 Mon, 22 Aug 2016 22:19:00 +0000 Lithium clustering 0 2 <p>Attachment karaf.log_c1 has been added with description: karaf_c1.log</p> <p>Attachment karaf.log_c2 has been added with description: karaf_c2.log</p> <p>Attachment karaf.log_c3 has been added with description: karaf_c3.log</p> <p>If I'm understanding this correctly, you stopped 2 nodes and later restarted them and they re-joined with the existing node that was still running. This is how it's supposed to work. A node always looks for another node (listed in the seed nodes) to join on startup. </p> <p>The documentation you refer to talks about cluster islands forming when there is a network partition between nodes. In this case, after the nodes on the other side of the partition are deemed "down", then cluster islands can/will form.</p> Development External issue ID 4751 External issue URL Rank 0|i02qpb: