<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:39 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[CONTROLLER-1481] Singleton Cluster is not happened</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1481</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Cluster instances are 10.106.138.107, 10.106.138.111, 10.106.138.251&lt;/p&gt;

&lt;p&gt;Observation-1 :&lt;/p&gt;

&lt;p&gt;In 3 node cluster, If all nodes goes down and then restarted node (10.106.138.107) which node act as a leader when nodes are up. now achieved singleton cluster. the leader will be selected and this node act as singleton cluster&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://10.106.138.107:8181/jolokia/read/akka:type=Cluster&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://10.106.138.107:8181/jolokia/read/akka:type=Cluster&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;{&quot;timestamp&quot;:1452166117,&quot;status&quot;:200,&quot;request&quot;:&lt;/p&gt;
{&quot;mbean&quot;:&quot;akka:type=Cluster&quot;,&quot;type&quot;:&quot;read&quot;}
&lt;p&gt;,&quot;value&quot;:{&quot;Available&quot;:true,&quot;ClusterStatus&quot;:&quot;{\n  \&quot;self-address\&quot;: \&quot;akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550\&quot;,\n  \&quot;members\&quot;: [\n    &lt;/p&gt;
{\n      \&quot;address\&quot;: \&quot;akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550\&quot;,\n      \&quot;status\&quot;: \&quot;Up\&quot;\n    }
&lt;p&gt;\n  ],\n  \&quot;unreachable\&quot;: &lt;span class=&quot;error&quot;&gt;&amp;#91;\n    \n  &amp;#93;&lt;/span&gt;\n}\n&quot;,&quot;Unreachable&quot;:&quot;&quot;,&quot;Members&quot;:&quot;akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550&quot;,&quot;Leader&quot;:&quot;akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550&quot;,&quot;MemberStatus&quot;:&quot;Up&quot;,&quot;Singleton&quot;:true}}&lt;/p&gt;

&lt;p&gt;Observation-2 :&lt;/p&gt;

&lt;p&gt;All 3 nodes goes down and then restarted any one of the non-leader node (10.106.138.251 and 10.106.138.111), leader will not be elected and not achieved singleton cluster.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://10.106.138.251:8181/jolokia/read/akka:type=Cluster&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://10.106.138.251:8181/jolokia/read/akka:type=Cluster&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;{&quot;timestamp&quot;:1452182366,&quot;status&quot;:200,&quot;request&quot;:&lt;/p&gt;
{&quot;mbean&quot;:&quot;akka:type=Cluster&quot;,&quot;type&quot;:&quot;read&quot;}
&lt;p&gt;,&quot;value&quot;:{&quot;Available&quot;:false,&quot;ClusterStatus&quot;:&quot;&lt;/p&gt;
{\n  \&quot;self-address\&quot;: \&quot;akka.tcp:\/\/opendaylight-cluster-data@10.106.138.251:2550\&quot;,\n  \&quot;members\&quot;: [\n    \n  ],\n  \&quot;unreachable\&quot;: [\n    \n  ]\n}
&lt;p&gt;\n&quot;,&quot;Unreachable&quot;:&quot;&quot;,&quot;Members&quot;:&quot;&quot;,&quot;Leader&quot;:&quot;&quot;,&quot;MemberStatus&quot;:&quot;Removed&quot;,&quot;Singleton&quot;:false}}&lt;/p&gt;


&lt;p&gt;&lt;a href=&quot;http://10.106.138.111:8181/jolokia/read/akka:type=Cluster&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://10.106.138.111:8181/jolokia/read/akka:type=Cluster&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;{&quot;timestamp&quot;:1452165274,&quot;status&quot;:200,&quot;request&quot;:&lt;/p&gt;
{&quot;mbean&quot;:&quot;akka:type=Cluster&quot;,&quot;type&quot;:&quot;read&quot;}
&lt;p&gt;,&quot;value&quot;:{&quot;Available&quot;:false,&quot;ClusterStatus&quot;:&quot;&lt;/p&gt;
{\n  \&quot;self-address\&quot;: \&quot;akka.tcp:\/\/opendaylight-cluster-data@10.106.138.111:2550\&quot;,\n  \&quot;members\&quot;: [\n    \n  ],\n  \&quot;unreachable\&quot;: [\n    \n  ]\n}
&lt;p&gt;\n&quot;,&quot;Unreachable&quot;:&quot;&quot;,&quot;Members&quot;:&quot;&quot;,&quot;Leader&quot;:&quot;&quot;,&quot;MemberStatus&quot;:&quot;Removed&quot;,&quot;Singleton&quot;:false}}&lt;/p&gt;


&lt;p&gt;Many times I have tried but got above observations only.&lt;/p&gt;

&lt;p&gt;Reproduce this issue, following below steps&lt;br/&gt;
1) 3-node is up&lt;br/&gt;
2) After election one node elected as a leader, then down all 3 nodes&lt;br/&gt;
3) Restart any one down node which is not act as a leader.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26035">CONTROLLER-1481</key>
            <summary>Singleton Cluster is not happened</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Cannot Reproduce</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ranjithkumar_t@hcl.com">ranjithkumar_t</reporter>
                        <labels>
                    </labels>
                <created>Thu, 4 Feb 2016 13:12:59 +0000</created>
                <updated>Thu, 19 Oct 2017 21:26:57 +0000</updated>
                            <resolved>Thu, 4 Feb 2016 13:30:13 +0000</resolved>
                                    <version>Beryllium</version>
                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="51256" author="ranjithkumar_t@hcl.com" created="Thu, 4 Feb 2016 13:12:59 +0000"  >&lt;p&gt;Attachment akka.conf has been added with description: For your reference i have attached akka.conf file&lt;/p&gt;</comment>
                            <comment id="51255" author="tpantelis" created="Thu, 4 Feb 2016 13:30:13 +0000"  >&lt;p&gt;This is due to the special nature of the first seed node in the list: 10.106.138.107. The first seed node must be up in order for the other seed nodes to form a cluster (observation 2). For observation 1, the first seed node will try to contact and join another seed node. If that fails then it will join itself and form a cluster. This is governed by the seed-node-timeout in the cluster section of the akka.conf - akka&apos;s default is 5s but we&apos;ve seen in some environments it needs to be increased to avoid cluster islands. &lt;/p&gt;

&lt;p&gt;In Be, we set the default for seed-node-timeout to 12s in the akka.conf that we ship. This alleviated the issue on the systems we had observed it. This was back ported to Li by &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/29347/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/29347/&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The attached akka.conf doesn&apos;t have the seed-node-timeout setting and it also contains the odl-cluster-rpc section which was removed in Be. I don&apos;t know what version you&apos;re using but you need to update your akka.conf. If 12s isn&apos;t enough in your environment then increase it further.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13565" name="akka.conf" size="2660" author="ranjithkumar_t@hcl.com" created="Thu, 4 Feb 2016 13:12:59 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5232</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=5232]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02qu7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>