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-766 OpenFlowPlugin <p>The switch scalability test, even when showing the issue sometimes, it has stabilize the max number:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-scalability-daily-only-boron/plot/Inventory%20Scalability/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-scalability-daily-only-boron/plot/Inventory%20Scalability/</a></p> <p>BR/Luis</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-766

Switch scalability test issue

Bug Resolved Done Luis Gomez Jozef Bacigal Thu, 8 Sep 2016 07:25:47 +0000 Mon, 27 Sep 2021 09:01:54 +0000 Mon, 3 Oct 2016 16:59:32 +0000 General 0 1 <p>FYI, I updated mininet image for this test to use latest OVS 2.5. Hopefully this adds more stability.</p> <p>The bug will remain open until we understand why Beryllium (old plugin) can scale up to 500 switches with no issues and Boron cannot.</p> <p>After changing to OVS 2.5, I get almost fix max=400 switches which I think it has been always the limit for Li plugin, so reducing the priority to normal in case you want to continue with this bug.</p> <p>FYI the ERROR I see when # of switches ~450 is:</p> <p>16-09-09 23:12:17,263 | ERROR | pool-32-thread-1 | SalRoleServiceImpl | 183 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | SetRoleService set Role BECOMEMASTER for Node: KeyedInstanceIdentifier</p> {targetType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey [_id=Uri [_value=openflow:151]]]]} <p> fail . Reason java.util.concurrent.CancellationException: Task was cancelled.<br/> 2016-09-09 23:12:17,268 | ERROR | n-dispatcher-203 | OutboundQueueProviderImpl | 183 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | No queue present, failing request<br/> 2016-09-09 23:12:17,272 | ERROR | n-dispatcher-106 | OutboundQueueProviderImpl | 183 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | No queue present, failing request</p> <p>master</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/45384/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/45384/</a></p> <p>boron</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/45712/1" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/45712/1</a></p> <p>This is fixed now. We see 500 switches (max in the test) for most of the time.</p> Duplicate OPNFLWPLUG-729 Development External issue ID 6665 External issue URL Issue Type ODL SR Target Milestone Rank 0|i0336f: