<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:44 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>[NETCONF-723] scale CSIT taking longer than 6 hours</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-723</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;It seems that netconf scale for max devices has &lt;a href=&quot;https://jenkins.opendaylight.org/releng/job/netconf-csit-1node-scale-max-devices-only-aluminium/plot/Netconf%20Devices/getPlot?index=0&amp;amp;width=750&amp;amp;height=450&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;improved recently &lt;/a&gt; , but also the&lt;br/&gt;
job has taken &lt;a href=&quot;https://jenkins.opendaylight.org/releng/job/netconf-csit-1node-scale-max-devices-only-aluminium/buildTimeTrend&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;over 6 hours &lt;/a&gt; to complete (so it aborts) in the past two iterations.&lt;br/&gt;
normally it takes ~3 hours.&lt;/p&gt;

&lt;p&gt;This ticket is to track that investigation. It could be related to the infra being&lt;br/&gt;
slow, or a real bottleneck in the controller and/or testtool.&lt;/p&gt;</description>
                <environment></environment>
        <key id="33226">NETCONF-723</key>
            <summary>scale CSIT taking longer than 6 hours</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="1" iconUrl="https://jira.opendaylight.org/images/icons/priorities/blocker.svg">Highest</priority>
                        <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="jluhrsen">Jamo Luhrsen</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                    </labels>
                <created>Fri, 11 Sep 2020 16:58:04 +0000</created>
                <updated>Tue, 15 Sep 2020 23:09:12 +0000</updated>
                            <resolved>Tue, 15 Sep 2020 23:09:12 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="68614" author="jluhrsen" created="Fri, 11 Sep 2020 17:01:23 +0000"  >&lt;p&gt;testing in the sandbox with double (12 hours) the timeout. Potentially the larger iteration that we are now&lt;br/&gt;
getting to because of the scale improvement takes much longer.&lt;/p&gt;</comment>
                            <comment id="68618" author="jluhrsen" created="Tue, 15 Sep 2020 23:09:12 +0000"  >&lt;p&gt;This is not a bug, but actually proof of a nice scale improvement.&lt;/p&gt;

&lt;p&gt;We are running up against the max configured @ 950 devices and each&lt;br/&gt;
iteration takes longer and longer to complete. Sometimes it takes longer&lt;br/&gt;
than 6 hours at which point the job aborts.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/c/releng/builder/+/92453&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Here is a patch &lt;/a&gt;  to increase those job parameters and we should be&lt;br/&gt;
able to see the new limits.&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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03ut3:</customfieldvalue>

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