<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:54:07 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-883] Clustering : Network Seg  (&gt; seconds ) between cluster nodes requires restart</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-883</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Establish a three node odl-mdsal-clustering cluster, then turn off the NIC on one of the nodes for 15 seconds or so... then turn it back on.&lt;/p&gt;

&lt;p&gt;The temporarily lost node will not successfully reconnect until it&apos;s controller process is restarted, apparently by design based on the INFO log messages.&lt;/p&gt;

&lt;p&gt;I&apos;m not sure why the restart is required, but if this remains necessary then we&apos;ll need the node to auto-restart itself if it detects that it&apos;s being quarantined for lack of restart.&lt;/p&gt;

&lt;p&gt;Especially in lab situations where clustering confidence is first established, switches get shutdown for more then 15 seconds frequently, and our SDN controller&apos;s cluster should auto-recover from this, preferably without orchestration hacks to cover for it.&lt;/p&gt;

&lt;p&gt;2014-09-22 14:02:42,521 | WARN  | lt-dispatcher-17 | Remoting                         | 234 - com.typesafe.akka.slf4j - 2.3.4 | Tried to associate with unreachable remote address &lt;span class=&quot;error&quot;&gt;&amp;#91;akka.tcp://opendaylight-cluster-data@192.168.1.26:2550&amp;#93;&lt;/span&gt;. Address is now gated for 5000 ms, all messages to this address will be delivered to dead letters. Reason: The remote system has quarantined this system. No further associations to the remote system are possible until this system is restarted.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25437">CONTROLLER-883</key>
            <summary>Clustering : Network Seg  (&gt; seconds ) between cluster nodes requires restart</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="10002">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="jameshall03885@gmail.com">James Gregory Hall</reporter>
                        <labels>
                    </labels>
                <created>Mon, 22 Sep 2014 21:20:56 +0000</created>
                <updated>Thu, 19 Oct 2017 21:26:52 +0000</updated>
                            <resolved>Tue, 18 Aug 2015 15:39:46 +0000</resolved>
                                    <version>Helium</version>
                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="49333" author="mark.mozolewski@hp.com" created="Sat, 7 Feb 2015 00:20:40 +0000"  >&lt;p&gt;James, the Quarantine behavior you are seeing is part of the lifecycle and failure model of the Akka framework. The Clustering team will have to discuss how we want to approach this long term since there are larger questions about network partition behavior, etc. I will drive that and own this bug. &lt;/p&gt;

&lt;p&gt;Note that ultimately the restart that is needed is just on the instances of the Akka systems (2 on each controller for data and rpcs) and should not be the controller as a whole. But since there is no mechanism for that now you would have to restart the controller. There is a local workaround: &lt;/p&gt;

&lt;p&gt;You can disable this behavior by commenting out the 2 occurrences of the following line in your ${karaf.home}/configuration/initial/akka.conf file (by prepending with &#8220;//&#8220;). With this change Akka will not Quarantine nodes for your testing/development. &lt;/p&gt;

&lt;p&gt;I&#8217;ve confirmed on 3 local VMs that this works for disabling/enabling a node&apos;s NIC.&lt;/p&gt;</comment>
                            <comment id="49334" author="mark.mozolewski@hp.com" created="Mon, 9 Feb 2015 21:37:47 +0000"  >&lt;p&gt;(In reply to Mark Mozolewski from comment #1)&lt;br/&gt;
&amp;gt; James, the Quarantine behavior you are seeing is part of the lifecycle and&lt;br/&gt;
&amp;gt; failure model of the Akka framework. The Clustering team will have to&lt;br/&gt;
&amp;gt; discuss how we want to approach this long term since there are larger&lt;br/&gt;
&amp;gt; questions about network partition behavior, etc. I will drive that and own&lt;br/&gt;
&amp;gt; this bug. &lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Note that ultimately the restart that is needed is just on the instances of&lt;br/&gt;
&amp;gt; the Akka systems (2 on each controller for data and rpcs) and should not be&lt;br/&gt;
&amp;gt; the controller as a whole. But since there is no mechanism for that now you&lt;br/&gt;
&amp;gt; would have to restart the controller. There is a local workaround: &lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; You can disable this behavior by commenting out the 2 occurrences of the&lt;br/&gt;
&amp;gt; following line in your ${karaf.home}/configuration/initial/akka.conf file&lt;br/&gt;
&amp;gt; (by prepending with &#8220;//&#8220;). &lt;/p&gt;

&lt;p&gt;//      auto-down-unreachable-after = 10s&lt;/p&gt;

&lt;p&gt;&amp;gt; With this change Akka will not Quarantine nodes&lt;br/&gt;
&amp;gt; for your testing/development. &lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; I&#8217;ve confirmed on 3 local VMs that this works for disabling/enabling a&lt;br/&gt;
&amp;gt; node&apos;s NIC.&lt;/p&gt;</comment>
                            <comment id="49335" author="mark.mozolewski@hp.com" created="Wed, 11 Feb 2015 23:57:06 +0000"  >&lt;p&gt;Proposal to increase default auto-down time while we plan overall auto-down behavior for clustering.&lt;/p&gt;


&lt;p&gt;(Controller) &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/15117&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/15117&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;(*Integration) &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/15175/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/15175/&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;For cluster deploy scripts to match akka.conf.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="49336" author="moraja@cisco.com" created="Tue, 18 Aug 2015 15:39:46 +0000"  >&lt;p&gt;4037 has more details of the problems caused by turning auto-down-after-unreachable&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="25950">CONTROLLER-1396</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="25656">CONTROLLER-1102</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </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>2035</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=2035]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10317"><![CDATA[Beryllium]]></customfieldvalue>

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

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