<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:54:09 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-895] Stats not being collected from all nodes, dangling nodes left in oper data store after mininet disconnects</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-895</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Two intermittent issues are being observed with mininets with a large number of nodes:&lt;/p&gt;

&lt;p&gt;1. Statistics are not being collected for some nodes. Everything else seems to be working fine, but a for a few nodes stats are not being collected. &lt;/p&gt;

&lt;p&gt;2. When mininet exits, one or two nodes are left &quot;dangling&quot; in the oper space. Note that the inventory data (node connector, the node core data, etc.) are deleted, only statistics are left behind (most of the time just a partial set of table stats, e.g. 145 empty tables out of 254). Connecting/disconnecting mininet of the same size clears the condition. (i.e. where the dangling &apos;shadow&apos; node is re-discovered, the old dangling stats are overwritten by a newly collected set of stats).&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25449">CONTROLLER-895</key>
            <summary>Stats not being collected from all nodes, dangling nodes left in oper data store after mininet disconnects</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="10000">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="jmedved@cisco.com">Jan Medved</reporter>
                        <labels>
                    </labels>
                <created>Thu, 25 Sep 2014 06:03:03 +0000</created>
                <updated>Thu, 19 Oct 2017 22:13:22 +0000</updated>
                            <resolved>Tue, 5 May 2015 15:17:21 +0000</resolved>
                                    <version>Helium</version>
                                                    <component>adsal</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="49398" author="jmedved@cisco.com" created="Thu, 25 Sep 2014 06:56:51 +0000"  >&lt;p&gt;In addition, in large mininets bulk flow delete is leaving dangling flows in one or more nodes&lt;/p&gt;</comment>
                            <comment id="49399" author="jmedved@cisco.com" created="Thu, 25 Sep 2014 06:59:43 +0000"  >&lt;p&gt;Sometimes it is inventory data that is not cleaned up. For example:&lt;/p&gt;

&lt;p&gt;{&lt;br/&gt;
-nodes: {&lt;br/&gt;
-node: [&lt;br/&gt;
-{&lt;br/&gt;
id: &quot;openflow:56&quot;&lt;br/&gt;
-node-connector: [&lt;br/&gt;
-{&lt;br/&gt;
id: &quot;openflow:56:3&quot;&lt;br/&gt;
flow-node-inventory:port-number: &quot;3&quot;&lt;br/&gt;
flow-node-inventory:supported: &quot;&quot;&lt;br/&gt;
flow-node-inventory:advertised-features: &quot;&quot;&lt;br/&gt;
flow-node-inventory:configuration: &quot;PORT-DOWN&quot;&lt;br/&gt;
flow-node-inventory:current-feature: &quot;&quot;&lt;br/&gt;
flow-node-inventory:current-speed: 0&lt;br/&gt;
flow-node-inventory:maximum-speed: 0&lt;br/&gt;
flow-node-inventory:hardware-address: &quot;DA:6E:F5:DE:3E:C9&quot;&lt;br/&gt;
flow-node-inventory:peer-features: &quot;&quot;&lt;br/&gt;
flow-node-inventory:name: &quot;s56-eth3&quot;&lt;br/&gt;
-flow-node-inventory:state: {&lt;br/&gt;
live: false&lt;br/&gt;
blocked: false&lt;br/&gt;
link-down: true&lt;br/&gt;
}&lt;br/&gt;
}&lt;br/&gt;
]&lt;br/&gt;
}&lt;br/&gt;
]&lt;br/&gt;
}&lt;br/&gt;
}&lt;/p&gt;</comment>
                            <comment id="49400" author="colin@colindixon.com" created="Sun, 28 Sep 2014 21:26:17 +0000"  >&lt;p&gt;The second half of this bug (lingering nodes in operational store) is effectively a duplicate of 2089 and 2091.&lt;/p&gt;

&lt;p&gt;The first half (stats not being collected) could still be occurring, but it would be good if Jan could confirm that it is and, if it&apos;s, not close the bug.&lt;/p&gt;</comment>
                            <comment id="49401" author="vdemcak@cisco.com" created="Thu, 2 Oct 2014 18:25:40 +0000"  >&lt;p&gt;I hope this bug is solved by &lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/11664/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/11664/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="49402" author="carolsand@gmail.com" created="Tue, 5 May 2015 15:17:21 +0000"  >&lt;p&gt;This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.&lt;/p&gt;</comment>
                    </comments>
                    <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>2078</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=2078]]></customfieldvalue>

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

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