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-588 OpenFlowPlugin <p>Build used : <br/> ===================<br/> Karaf distro from latest ODL Beryllium master code</p> <p>Test Type : <br/> ===================<br/> switch state resync after cluster node restart.</p> <p>Objective of test : <br/> ===================<br/> verify switch resync when node is restarted. </p> <p>Test Steps :<br/> ============<br/> 1. Bring up healthy 3 node cluster say c1, c2 and c3. c1 is leader. <br/> 2. connect OVS switch to c3 node. c3 node is entity owner as shown in attached snapshot.<br/> 3. push 10 flows using flow-config-blaster script from follower c3<br/> 4. total flows in switch, config DS and operational DS is 10<br/> 5. restart c3 node<br/> 6. connect OVS switch to c3 node, c3 node is entity owner as shown in attached snapshot.<br/> 7. switch is showing 2 flows <br/> 8. config DS is showing 10 flows and Operational DS is showing 2 flows</p> <p>Note: Output shown for Flows in switch and Operational DS in Step 7 and Step 8 are not consistent. In 4 times, i have seen output as 4, 0, 10 and 2 flows.</p> <p>Controllers (to cross-check logs):<br/> ===================================<br/> c1 - Controller 1 with IP 10.183.181.41 - config-inventory-shard leader<br/> c2 - Controller 2 with IP 10.183.181.42 - config-inventory-shard follower<br/> c3 - Controller 3 with IP 10.183.181.43 - config-inventory-shard follower </p> <p>Enclosed Logs:<br/> ==============<br/> c1.karaf.log for controller c1<br/> c2.karaf.log for controller c2<br/> c3.karaf.log for controller c3<br/> snapshot for entity ower from c3<br/> snapshot for flows in OVS switch</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-588

[Clustering]: Switch state resync is not happening after controller restart [Routed RPC issue]

Bug Resolved Done Unassigned Anil Gujele Mon, 4 Jan 2016 11:15:27 +0000 Mon, 27 Sep 2021 09:01:41 +0000 Thu, 11 Feb 2016 08:10:54 +0000 General 0 9 <p>Attachment resyncFailed.rar has been added with description: attached snapshot and logs from c1, c2,c3 node.</p> <p>In above description, "leader" indicates shard-leader of inventory-config shard and "follower" indicates follower(s) of inventory-config</p> <p>Looks like this should be filed against the openflow or ovsdb project.</p> <p>changed product from controller to openflowplugin</p> <p>Tom/Moiz,</p> <p>This is another scenario of Routed RPC failure, which we are discussing through some other bugs.</p> <p>Hi Muthu,</p> <p>I pushed following patch to openflowplugin that should solve/workaround this issue. My patch basically avoiding routed rpc by using clustering DCN + local rpc registration.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/34115/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34115/</a></p> <p>Can you please test with this patch and see if this works for you.</p> <p>Patch looks fine with me Anil. We will pick this and test. So, we have fully eliminated the need for forcing reconciliation through routed-rpc</p> <p>Yes and i think it's probably better in term of performance. Hopefully you will see some performance improvement in flow/second in clustered setup, given that we are avoiding remote rpc now and assuming that ClusteredData(Change/Tree)Listner don't create much problem. And once we get rid of DataChangeListner and use TreeListner, things might improve further.</p> <p>Although Anil's patch removes the use of routed RPCs in OF, we should fix the timing issue with RPCs so I submitted <a href="https://git.opendaylight.org/gerrit/#/c/34175/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34175/</a> to add wait/retries in the RPC code.</p> <p>Is this "Waiting for Review" now? It looks like Tom Pantelis pushed a patch to fix this.</p> <p>Also, are we targeting stable/beryllium as well?</p> <p>Spawning a separate bug for:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/34175/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34175/</a> </p> <p>This adds wait/retries in the RPC code.</p> <p>I have verified with latest code build,<br/> I can see switch, config DS and Operational DS are showing same number of flows after follower node restart.</p> Duplicate CONTROLLER-1467 Development External issue ID 4866 External issue URL Priority Rank 0|i0322v: