<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:24 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-1766] The RaftState of one cluster node changed to &apos;IsolatedLeader&apos; after a large number of Virtual NWs were created.</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1766</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;After a large number of Virtual NWs were created, the RaftState of one cluster node became abnormal.&lt;br/&gt;
It changed from  Leader to IsolatedLeader, Follower to Candidate.&lt;br/&gt;
Then RaftState not changed even after 16 hours.&lt;br/&gt;
And the RaftState of other 2 nodes did not changed at all.&lt;/p&gt;

&lt;p&gt;Environment Details:&lt;br/&gt;
  OpenStack Version: stable/ocata&lt;br/&gt;
  ODL Version: carbon-FR + L2GW related patches&lt;br/&gt;
  ODL&#12398;MAX heap: JAVA_MAX_MEM=&quot;6144m&quot;&lt;/p&gt;

&lt;p&gt;Reproduction steps:&lt;br/&gt;
  1. Initialization and set up of Controller/Compute/L2GW Node&lt;br/&gt;
  2. Creation of 1000 virtual NWs&lt;br/&gt;
  3. Creation of 1 L2GW GATEWAY&lt;br/&gt;
  4. Creation of 1000 L2GW CONNECTIONs&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;This phenomenon does not always occur (occurrence ratio:  1/3)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Karaf logs:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Split Karaf logs are attached.&lt;br/&gt;
    The time when RaftState became abnormal is around 17: 20-17: 23.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;odl1# &lt;br/&gt;
karaf.log.3:2017-08-08 13:28:41,123 | INFO  | lt-dispatcher-22 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier:akka.tcp://opendaylight-cluster-data@192.168.101.8:2550/user/shardmanager-operational/member-1-shard-topology-operational/member-1-shard-topology-operational-notifier#1974074480 created and ready for shard:member-1-shard-topology-operational&lt;br/&gt;
karaf.log.3:2017-08-08 13:28:41,131 | INFO  | lt-dispatcher-23 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-1-shard-topology-operational , received role change from null to Follower&lt;br/&gt;
karaf.log.3:2017-08-08 13:28:41,132 | INFO  | lt-dispatcher-23 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-1-shard-topology-operational , registered listener akka://opendaylight-cluster-data/user/shardmanager-operational&lt;br/&gt;
karaf.log.3:2017-08-08 13:28:51,162 | INFO  | lt-dispatcher-36 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-1-shard-topology-operational , received role change from Follower to Candidate&lt;br/&gt;
karaf.log.3:2017-08-08 13:28:51,165 | INFO  | lt-dispatcher-41 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-1-shard-topology-operational , received role change from Candidate to Leader&lt;br/&gt;
karaf.log:2017-08-08 17:20:35,381 | INFO  | lt-dispatcher-45 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-1-shard-topology-operational , received role change from Leader to IsolatedLeader&lt;/p&gt;

&lt;p&gt;odl2#&lt;br/&gt;
karaf.log.1:2017-08-08 13:28:41,124 | INFO  | lt-dispatcher-23 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier:akka.tcp://opendaylight-cluster-data@192.168.101.13:2550/user/shardmanager-operational/member-2-shard-topology-operational/member-2-shard-topology-operational-notifier#-1501266548 created and ready for shard:member-2-shard-topology-operational&lt;br/&gt;
karaf.log.1:2017-08-08 13:28:41,130 | INFO  | ult-dispatcher-3 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-2-shard-topology-operational , received role change from null to Follower&lt;br/&gt;
karaf.log.1:2017-08-08 13:28:41,138 | INFO  | ult-dispatcher-3 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-2-shard-topology-operational , registered listener akka://opendaylight-cluster-data/user/shardmanager-operational&lt;br/&gt;
karaf.log:Caused by: akka.pattern.AskTimeoutException: Ask timed out on [ActorSelection&lt;span class=&quot;error&quot;&gt;&amp;#91;Anchor(akka.tcp://opendaylight-cluster-data@192.168.101.8:2550/), Path(/user/shardmanager-operational/member-1-shard-topology-operational/shard-topology-member-2:datastore-operational@0:89656_200508#2123488974)&amp;#93;&lt;/span&gt;] after &lt;span class=&quot;error&quot;&gt;&amp;#91;5000 ms&amp;#93;&lt;/span&gt;. Sender&lt;span class=&quot;error&quot;&gt;&amp;#91;null&amp;#93;&lt;/span&gt; sent message of type &quot;org.opendaylight.controller.cluster.datastore.messages.ReadData&quot;.&lt;br/&gt;
karaf.log:ReadFailedException{message=Error checking ReadData for path /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[&lt;/p&gt;
{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=hwvtep:1}
&lt;p&gt;]/node/node[&lt;/p&gt;
{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=hwvtep://uuid/44307ca2-4ebf-4470-8d06-7e377959a41c}
&lt;p&gt;]/AugmentationIdentifier&lt;/p&gt;
{childNames=[(urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)remote-ucast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)managers, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)local-mcast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)switches, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-routers, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)remote-arp-sources, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)local-ucast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-binding-stats, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)connection-info, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)acls, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)local-arp-sources, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)remote-mcast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-switches]}
&lt;p&gt;/(urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-switches/logical-switches[&lt;/p&gt;
{(urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)hwvtep-node-name=a40b416f-18c8-43a8-9466-7759d62e4ce4}
&lt;p&gt;], errorList=[RpcError [message=Error checking ReadData for path /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[&lt;/p&gt;
{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=hwvtep:1}
&lt;p&gt;]/node/node[&lt;/p&gt;
{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=hwvtep://uuid/44307ca2-4ebf-4470-8d06-7e377959a41c}
&lt;p&gt;]/AugmentationIdentifier&lt;/p&gt;
{childNames=[(urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)remote-ucast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)managers, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)local-mcast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)switches, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-routers, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)remote-arp-sources, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)local-ucast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-binding-stats, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)connection-info, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)acls, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)local-arp-sources, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)remote-mcast-macs, (urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-switches]}
&lt;p&gt;/(urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)logical-switches/logical-switches[&lt;/p&gt;
{(urn:opendaylight:params:xml:ns:yang:ovsdb:hwvtep?revision=2015-09-01)hwvtep-node-name=a40b416f-18c8-43a8-9466-7759d62e4ce4}
&lt;p&gt;], severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=akka.pattern.AskTimeoutException: Ask timed out on [ActorSelection&lt;span class=&quot;error&quot;&gt;&amp;#91;Anchor(akka.tcp://opendaylight-cluster-data@192.168.101.8:2550/), Path(/user/shardmanager-operational/member-1-shard-topology-operational/shard-topology-member-2:datastore-operational@0:89656_200508#2123488974)&amp;#93;&lt;/span&gt;] after &lt;span class=&quot;error&quot;&gt;&amp;#91;5000 ms&amp;#93;&lt;/span&gt;. Sender&lt;span class=&quot;error&quot;&gt;&amp;#91;null&amp;#93;&lt;/span&gt; sent message of type &quot;org.opendaylight.controller.cluster.datastore.messages.ReadData&quot;.]]}&lt;/p&gt;

&lt;p&gt;odl3# &lt;br/&gt;
2017-08-08 13:28:41,130 | INFO  | lt-dispatcher-20 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier:akka.tcp://opendaylight-cluster-data@192.168.101.15:2550/user/shardmanager-operational/member-3-shard-topology-operational/member-3-shard-topology-operational-notifier#1779121060 created and ready for shard:member-3-shard-topology-operational&lt;br/&gt;
2017-08-08 13:28:41,142 | INFO  | lt-dispatcher-22 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-3-shard-topology-operational , received role change from null to Follower&lt;br/&gt;
2017-08-08 13:28:41,142 | INFO  | lt-dispatcher-48 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-3-shard-topology-operational , registered listener akka://opendaylight-cluster-data/user/shardmanager-operational&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26320">CONTROLLER-1766</key>
            <summary>The RaftState of one cluster node changed to &apos;IsolatedLeader&apos; after a large number of Virtual NWs were created.</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="10003" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Confirmed</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ran-xiao@vf.jp.nec.com">Ran Xiao</reporter>
                        <labels>
                    </labels>
                <created>Mon, 4 Sep 2017 02:26:59 +0000</created>
                <updated>Tue, 1 Oct 2019 20:20:54 +0000</updated>
                                            <version>Carbon</version>
                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>10</watches>
                                                                                                                <comments>
                            <comment id="52698" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:27:58 +0000"  >&lt;p&gt;Attachment xaa has been added with description: Karaf log 1&lt;/p&gt;</comment>
                            <comment id="52699" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:28:26 +0000"  >&lt;p&gt;Attachment xab has been added with description: Karaf log 2&lt;/p&gt;</comment>
                            <comment id="52700" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:28:59 +0000"  >&lt;p&gt;Attachment xac has been added with description: Karaf log 3&lt;/p&gt;</comment>
                            <comment id="52701" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:31:34 +0000"  >&lt;p&gt;Attachment xad has been added with description: Karaf log 4&lt;/p&gt;</comment>
                            <comment id="52702" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:32:07 +0000"  >&lt;p&gt;Attachment xae has been added with description: Karaf log 5&lt;/p&gt;</comment>
                            <comment id="52703" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:32:34 +0000"  >&lt;p&gt;Attachment xaf has been added with description: Karaf log 6&lt;/p&gt;</comment>
                            <comment id="52694" author="tpantelis" created="Fri, 8 Sep 2017 19:00:26 +0000"  >&lt;p&gt;The attached logs are in some binary format. Are they zipped? If so what format - the first one attached was just named &quot;xaa&quot;. &lt;/p&gt;

&lt;p&gt;There are 6 attachments - does that mean it&apos;s a 6-node cluster?&lt;/p&gt;

&lt;p&gt;The change from Leader to IsolatedLeader indicates the leader lost connection to a majority of the followers, or at least did not receive heartbeat replies for a period of time.&lt;/p&gt;</comment>
                            <comment id="52695" author="ran-xiao@vf.jp.nec.com" created="Mon, 11 Sep 2017 01:09:17 +0000"  >&lt;p&gt;(In reply to Tom Pantelis from comment #7)&lt;/p&gt;

&lt;p&gt;Hi Tom,&lt;/p&gt;

&lt;p&gt;Sorry for not having discribed it clearly.&lt;br/&gt;
Log files are zipped and split(6 parts), as the size of attachment is limited.&lt;br/&gt;
For checking logs, pls download all these 6 files, and run the command below:&lt;br/&gt;
 cat xaa .. xaf &amp;gt; odl.tar.xz &lt;br/&gt;
 tar Jxvf odl.tar.xz &lt;/p&gt;

&lt;p&gt;This is a 3-node cluster.&lt;/p&gt;

&lt;p&gt;&amp;gt;&amp;gt;The change from Leader to IsolatedLeader indicates the leader lost connection to a majority of the followers,or at least did not receive heartbeat replies for a period of time.&lt;br/&gt;
How long is this &quot;a period of time&#8221;?&lt;br/&gt;
How is it set? Is it set by magic number or config parameter?&lt;/p&gt;

&lt;p&gt;After the state changed into IsolatedLeader does the situation that the cluster cannot return to normal states happen?&lt;br/&gt;
For example, does it cannot return after waited a period of time?&lt;/p&gt;</comment>
                            <comment id="52696" author="tpantelis" created="Tue, 12 Sep 2017 01:47:32 +0000"  >&lt;p&gt;(In reply to Ran Xiao from comment #8)&lt;br/&gt;
&amp;gt; (In reply to Tom Pantelis from comment #7)&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Hi Tom,&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Sorry for not having discribed it clearly.&lt;br/&gt;
&amp;gt; Log files are zipped and split(6 parts), as the size of attachment is&lt;br/&gt;
&amp;gt; limited.&lt;br/&gt;
&amp;gt; For checking logs, pls download all these 6 files, and run the command below:&lt;br/&gt;
&amp;gt;  cat xaa .. xaf &amp;gt; odl.tar.xz &lt;br/&gt;
&amp;gt;  tar Jxvf odl.tar.xz &lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; This is a 3-node cluster.&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; &amp;gt;&amp;gt;The change from Leader to IsolatedLeader indicates the leader lost connection to a majority of the followers,or at least did not receive heartbeat replies for a period of time.&lt;br/&gt;
&amp;gt; How long is this &quot;a period of time&#8221;?&lt;br/&gt;
&amp;gt; How is it set? Is it set by magic number or config parameter?&lt;br/&gt;
&amp;gt; &lt;/p&gt;

&lt;p&gt;10s by default. It is configurable.&lt;/p&gt;

&lt;p&gt;&amp;gt; After the state changed into IsolatedLeader does the situation that the&lt;br/&gt;
&amp;gt; cluster cannot return to normal states happen?&lt;br/&gt;
&amp;gt; For example, does it cannot return after waited a period of time?&lt;/p&gt;

&lt;p&gt;Once it regains connectivity to a majority of the followers it will transition back to Leader.&lt;/p&gt;

&lt;p&gt;In odl1 karaf.log, reachability with 192.168.101.8 flapped for a bit: &lt;/p&gt;

&lt;p&gt;2017-08-08 19:17:46,725 | WARN  | lt-dispatcher-29 | ClusterCoreDaemon                | 186 - com.typesafe.akka.slf4j - 2.4.17 | Cluster Node &lt;span class=&quot;error&quot;&gt;&amp;#91;akka.tcp://opendaylight-cluster-data@192.168.101.8:2550&amp;#93;&lt;/span&gt; - Marking node(s) as UNREACHABLE &lt;span class=&quot;error&quot;&gt;&amp;#91;Member(address = akka.tcp://opendaylight-cluster-data@192.168.101.13:2550, status = Up)&amp;#93;&lt;/span&gt;. Node roles &lt;span class=&quot;error&quot;&gt;&amp;#91;member-1&amp;#93;&lt;/span&gt;&lt;br/&gt;
2017-08-08 19:17:56,723 | INFO  | lt-dispatcher-40 | kka://opendaylight-cluster-data) | 186 - com.typesafe.akka.slf4j - 2.4.17 | Cluster Node &lt;span class=&quot;error&quot;&gt;&amp;#91;akka.tcp://opendaylight-cluster-data@192.168.101.8:2550&amp;#93;&lt;/span&gt; - Marking node(s) as REACHABLE &lt;span class=&quot;error&quot;&gt;&amp;#91;Member(address = akka.tcp://opendaylight-cluster-data@192.168.101.13:2550, status = Up)&amp;#93;&lt;/span&gt;. Node roles &lt;span class=&quot;error&quot;&gt;&amp;#91;member-1&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;It seems that once it went to IsolatedLeader, it never again received a heartbeat response from a follower. It could be due to load - it would be beneficial to monitor the CPU/memory usage and GC activity. Also thread dumps on the followers - perhaps there&apos;s a stuck thread. &lt;/p&gt;

&lt;p&gt;Re: the logging, this is the only message I see on odl1 w.r.t IsolatedLeader:&lt;/p&gt;

&lt;p&gt;karaf.log:2017-08-08 17:20:35,312 | INFO  | lt-dispatcher-60 | RoleChangeNotifier               | 204 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.Carbon | RoleChangeNotifier for member-1-shard-inventory-config , received role change from Leader to IsolatedLeader&lt;/p&gt;

&lt;p&gt;This is odd b/c there should be additional logging (INFO/WARN), ie&lt;/p&gt;

&lt;p&gt;&quot;Switching from behavior Leader to IsolatedLeader ...&quot;&lt;br/&gt;
&quot;At least {} followers need to be active, Switching {} from Leader to IsolatedLeader&quot;&lt;/p&gt;

&lt;p&gt;It seems there&apos;s missing logging or the upstream clustering code has been forked...&lt;/p&gt;</comment>
                            <comment id="52704" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:07:24 +0000"  >&lt;p&gt;Attachment karaf_odl1_20170921085857.tar.xz.aa has been added with description: karaf_odl1_20170921085857.tar.xz.aa   odl1 karaf.log part 1&lt;/p&gt;</comment>
                            <comment id="52705" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:08:24 +0000"  >&lt;p&gt;Attachment karaf_odl1_20170921085857.tar.xz.ab has been added with description: karaf_odl1_20170921085857.tar.xz.ab   odl1 karaf.log part 2&lt;/p&gt;</comment>
                            <comment id="52706" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:08:53 +0000"  >&lt;p&gt;Attachment karaf_odl1_20170921085857.tar.xz.ac has been added with description: karaf_odl1_20170921085857.tar.xz.ac   odl1 karaf.log part 3&lt;/p&gt;</comment>
                            <comment id="52707" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:09:17 +0000"  >&lt;p&gt;Attachment karaf_odl2_20170921090305.tar.xz.aa has been added with description: karaf_odl2_20170921090305.tar.xz.aa   odl2 karaf.log part 1&lt;/p&gt;</comment>
                            <comment id="52708" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:09:38 +0000"  >&lt;p&gt;Attachment karaf_odl2_20170921090305.tar.xz.ab has been added with description: karaf_odl2_20170921090305.tar.xz.ab   odl2 karaf.log part 2&lt;/p&gt;</comment>
                            <comment id="52709" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:10:20 +0000"  >&lt;p&gt;Attachment karaf_odl3_20170921091358.tar.xz.aa has been added with description: karaf_odl3_20170921091358.tar.xz.aa   odl3 karaf.log part 1&lt;/p&gt;</comment>
                            <comment id="52710" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:10:38 +0000"  >&lt;p&gt;Attachment karaf_odl3_20170921091358.tar.xz.ab has been added with description: karaf_odl3_20170921091358.tar.xz.ab   odl3 karaf.log part 2&lt;/p&gt;</comment>
                            <comment id="52711" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:11:06 +0000"  >&lt;p&gt;Attachment other.tar.xz has been added with description: other.tar.xz Various information&lt;/p&gt;</comment>
                            <comment id="52697" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:12:43 +0000"  >&lt;p&gt;(In reply to Tom Pantelis from comment #9)&lt;/p&gt;

&lt;p&gt;We reproduced this issue and collected the information mentioned above.&lt;/p&gt;

&lt;p&gt;The following seems to have occurred:&lt;br/&gt;
1. ODL process of ODL2 was stopped&lt;br/&gt;
2. ODL1 port: 2550 was closed&lt;br/&gt;
We think these caused the IsolatedLeader issue, right?&lt;/p&gt;

&lt;p&gt;We checked karaf log but cann&apos;t find out why the above two phenomenon occurred.&lt;br/&gt;
Do you have any idea?&lt;/p&gt;

&lt;p&gt;Attachment:&lt;br/&gt;
  karaf_odl1_20170921085857.tar.xz.aa   odl1 karaf.log part 1&lt;br/&gt;
  karaf_odl1_20170921085857.tar.xz.ab   odl1 karaf.log part 2&lt;br/&gt;
  karaf_odl1_20170921085857.tar.xz.ac   odl1 karaf.log part 3&lt;br/&gt;
  karaf_odl2_20170921090305.tar.xz.aa   odl2 karaf.log part 1&lt;br/&gt;
  karaf_odl2_20170921090305.tar.xz.ab   odl2 karaf.log part 2&lt;br/&gt;
  karaf_odl3_20170921091358.tar.xz.aa   odl3 karaf.log part 1&lt;br/&gt;
  karaf_odl3_20170921091358.tar.xz.ab   odl3 karaf.log part 2&lt;br/&gt;
  other.tar.xz                          Various information&lt;br/&gt;
                                        lsof -p &lt;/p&gt;
{ODL PID}
&lt;p&gt;                                        netstat -an&lt;br/&gt;
                                        ps -C java -L -o pcpu,cpu,nice,state,cputime,pid,tid | sort&lt;br/&gt;
                                        ps -ef(ps_odl&lt;span class=&quot;error&quot;&gt;&amp;#91;123&amp;#93;&lt;/span&gt;.txt)&lt;br/&gt;
                                        jstack &lt;/p&gt;
{ODL_PID}
&lt;p&gt;(threaddump_odl&lt;span class=&quot;error&quot;&gt;&amp;#91;13&amp;#93;&lt;/span&gt;.txt)&lt;br/&gt;
                                        top&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13691" name="karaf_odl1_20170921085857.tar.xz.aa" size="1024000" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:07:24 +0000"/>
                            <attachment id="13692" name="karaf_odl1_20170921085857.tar.xz.ab" size="1024000" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:08:24 +0000"/>
                            <attachment id="13693" name="karaf_odl1_20170921085857.tar.xz.ac" size="752624" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:08:53 +0000"/>
                            <attachment id="13694" name="karaf_odl2_20170921090305.tar.xz.aa" size="1024000" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:09:17 +0000"/>
                            <attachment id="13695" name="karaf_odl2_20170921090305.tar.xz.ab" size="558236" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:09:38 +0000"/>
                            <attachment id="13696" name="karaf_odl3_20170921091358.tar.xz.aa" size="1024000" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:10:20 +0000"/>
                            <attachment id="13697" name="karaf_odl3_20170921091358.tar.xz.ab" size="499032" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:10:38 +0000"/>
                            <attachment id="13698" name="other.tar.xz" size="43340" author="ran-xiao@vf.jp.nec.com" created="Fri, 22 Sep 2017 03:11:06 +0000"/>
                            <attachment id="13685" name="xaa" size="1000000" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:27:58 +0000"/>
                            <attachment id="13686" name="xab" size="1000000" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:28:26 +0000"/>
                            <attachment id="13687" name="xac" size="1000000" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:28:59 +0000"/>
                            <attachment id="13688" name="xad" size="1000000" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:31:34 +0000"/>
                            <attachment id="13689" name="xae" size="1000000" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:32:07 +0000"/>
                            <attachment id="13690" name="xaf" size="612276" author="ran-xiao@vf.jp.nec.com" created="Mon, 4 Sep 2017 02:32:34 +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>9090</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=9090]]></customfieldvalue>

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

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