<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:36:17 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>[OVSDB-397] operational datastore is missing for node if the ucast macs are high in the node</title>
                <link>https://jira.opendaylight.org/browse/OVSDB-397</link>
                <project id="10158" key="OVSDB">ovsdb</project>
                    <description>&lt;p&gt;If the device has more ucast macs (remote+local) say 4k&lt;br/&gt;
the monitor hardware table json rpc request is timing out ( default timer being 1sec ) and operational datastore for the node is not getting filled.&lt;/p&gt;

&lt;p&gt;Can we just increase the reaper interval timeout from 1 sec ?&lt;br/&gt;
Will that have some other side affects ?&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="22089">OVSDB-397</key>
            <summary>operational datastore is missing for node if the ucast macs are high in the node</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="k.v.suneelu.verma@ericsson.com">suneel verma</assignee>
                                    <reporter username="k.v.suneelu.verma@ericsson.com">suneel verma</reporter>
                        <labels>
                    </labels>
                <created>Thu, 19 Jan 2017 14:16:45 +0000</created>
                <updated>Wed, 1 May 2019 23:37:31 +0000</updated>
                            <resolved>Wed, 1 May 2019 23:37:31 +0000</resolved>
                                    <version>unspecified</version>
                                                    <component>Southbound.hw_vtep</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="41626" author="thapar" created="Mon, 23 Jan 2017 07:59:15 +0000"  >&lt;p&gt;Suneelu, did this get fixed as part of other/HA changes?&lt;/p&gt;</comment>
                            <comment id="41627" author="vishnoianil@gmail.com" created="Thu, 2 Feb 2017 22:59:00 +0000"  >&lt;p&gt;The only side effect it will have is that it will accumulate more future objects in wait state so memory consumption will increase.&lt;/p&gt;

&lt;p&gt;I believe 1 second is pretty long duration, but if your controller has enough heap space, increasing the reaper timeout (ovsdb-rpc-task-timeout) should be okay.&lt;/p&gt;</comment>
                            <comment id="41628" author="vishnoianil@gmail.com" created="Wed, 22 Feb 2017 00:46:42 +0000"  >&lt;p&gt;Hi Suneel,&lt;/p&gt;

&lt;p&gt;Any update on this patch? &lt;/p&gt;

&lt;p&gt;Thanks&lt;br/&gt;
Anil&lt;/p&gt;</comment>
                            <comment id="41629" author="daya_k" created="Tue, 7 Mar 2017 15:32:43 +0000"  >&lt;p&gt;we should check whether the delay is caused on the switch (ovs-vtep or physical), or in the plugin to do the unmarshalling of the msg.&lt;br/&gt;
can we also check if ovsdb protocol itself supports batching of large messages into smaller chunks&lt;/p&gt;</comment>
                            <comment id="66739" author="vishnoianil@gmail.com" created="Wed, 1 May 2019 23:37:31 +0000"  >&lt;p&gt;No activity on the bug for 2 years. Closing the bug, please re-open if you plan to work on it again.&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>7600</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=7600]]></customfieldvalue>

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

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