https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OPNFLWPLUG-597 OpenFlowPlugin <p>Current CI longevity test shows Li plugin goes out of memory after 20 runs of bringing 200 switches in the network:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-longevity-lithium-redesign-only-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-longevity-lithium-redesign-only-beryllium/</a></p> <p>BR/Luis</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-597

Longevity Li plugin: controller Out Of Memory after 20 runs

Bug Resolved Done Robert Varga Luis Gomez Tue, 19 Jan 2016 01:25:36 +0000 Mon, 27 Sep 2021 09:01:42 +0000 Sat, 30 Jan 2016 16:27:46 +0000 General 0 2 <p>Can we reconfigure the test to capture a memory dump?</p> <p>Memory allocation failure when creating a thread &#8211; this points to failure to allocate thread stack (8MB by default), which actually lies outside of the heap.</p> <p>2016-01-25 12:10:54,210 | INFO | ol-7903-thread-1 | SalRoleServiceImpl | 168 - org.opendaylight.openflowplugin.impl - 0.2.0.SNAPSHOT | RoleChangeTask called on device:openflow:124 OFPRole:BECOMEMASTER<br/> 2016-01-25 12:10:54,810 | INFO | ol-7905-thread-1 | SalRoleServiceImpl | 168 - org.opendaylight.openflowplugin.impl - 0.2.0.SNAPSHOT | RoleChangeTask called on device:openflow:125 OFPRole:BECOMEMASTER</p> <p>Noting the high sequence number, I suspect somebody somewhere is allocating threadpools and not shutting them down, leading to a huge number of threads which are sitting idle.</p> <p>Boils down to SalRoleServiceImpl allocating a single-threaded executor, which is not being closed at all.</p> <p>master: <a href="https://git.opendaylight.org/gerrit/33521" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/33521</a></p> <p>boron: <a href="https://git.opendaylight.org/gerrit/33521" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/33521</a><br/> boron: <a href="https://git.opendaylight.org/gerrit/33560" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/33560</a></p> <p>beryllium: <a href="https://git.opendaylight.org/gerrit/33551" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/33551</a><br/> beryllium: <a href="https://git.opendaylight.org/gerrit/33562" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/33562</a></p> <p>merged</p> <p>Robert, I do not know how you do in yangtools, but in openflowplugin project we ask the bug reporter person to restest before closing the bug.</p> <p>Well, this has been the workflow on all projects I have participated ever since OpenDaylight came to existence.</p> <p>What is the Bugzilla state for 'the patch merged, waiting for confirmation that the bug is gone' and what does the RESOLVED/VERIFIED state stand for? Is there a wiki page describing these for openflowplugin?</p> <p>OK, you are right, there is no project instruction as well as bugzilla does not seem to have the states for what I believe are good and common practices for bug/issue workflow. I hope this will be better handled in Jira.</p> Development External issue ID 5001 External issue URL Issue Type ODL SR Target Milestone Rank 0|i0324v: