OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [CONTROLLER-1336] Clustering: Persist data lost https://jira.opendaylight.org/browse/CONTROLLER-1336 controller <p>I used one node cluster.<br/> 1\First, I wrote data on path: <br/> InstanceIdentifier.builder(VirtualRouter.class)<br/> .child(Vr.class, new VrKey(vrId)).toInstance();<br/> I used put method. Restconf result is <br/> 1. &lt;virtual-router xmlns="urn:opendaylight:vipran:virtual-router"&gt;<br/> 2. &lt;vr&gt;<br/> 3. &lt;vr-id&gt;${vrname}&lt;/vr-id&gt;<br/> 4. &lt;vr-node-a&gt;<br/> 5. &lt;vr-node-id&gt;openflow:3&lt;/vr-node-id&gt;<br/> &lt;ip&gt;10.10.30.10&lt;/ip&gt;<br/> 6. &lt;/vr-node-a&gt;<br/> 7. &lt;vr-node-a&gt;<br/> 8. &lt;vr-node-id&gt;openflow:4&lt;/vr-node-id&gt;<br/> &lt;ip&gt;10.10.40.10&lt;/ip&gt;<br/> 9. &lt;/vr-node-a&gt;<br/> 10. &lt;topology-id&gt;${vrname}&lt;/topology-id&gt;<br/> 11. &lt;vr-node-b&gt;<br/> 12. &lt;vr-node-id&gt;openflow:1&lt;/vr-node-id&gt;<br/> &lt;ip&gt;10.10.10.10&lt;/ip&gt;<br/> 13. &lt;/vr-node-b&gt;<br/> 14. &lt;vr-node-b&gt;<br/> 15. &lt;vr-node-id&gt;openflow:2&lt;/vr-node-id&gt;<br/> &lt;ip&gt;10.10.20.10&lt;/ip&gt;<br/> 16. &lt;/vr-node-b&gt;<br/> 17. &lt;/vr&gt;<br/> 18. &lt;/virtual-router&gt;</p> <p>2\Then, I wrote data on path: <br/> InstanceIdentifier.builder(VirtualRouter.class)<br/> .child(Vr.class, new VrKey(uniIf.getVrId()))<br/> .child(VrNodeA.class, new VrNodeAKey(uniIf.getUniNode()))<br/> .child(VrNodeConnector.class, new VrNodeConnectorKey(uniIf.getUniPortName()))<br/> .child(NodeUniIf.class, new NodeUniIfKey(uniIf.getUniName())).toInstance();<br/> I used merge method. Restconf result is <br/> 1. &lt;virtual-router xmlns="urn:opendaylight:vipran:virtual-router"&gt;<br/> 2. &lt;vr&gt;<br/> 3. &lt;vr-id&gt;${vrname}&lt;/vr-id&gt;<br/> 4. &lt;topology-id&gt;${vrname}&lt;/topology-id&gt;<br/> 5. &lt;vr-node-a&gt;<br/> 6. &lt;vr-node-id&gt;openflow:3&lt;/vr-node-id&gt;<br/> 7. &lt;vr-node-connector&gt;<br/> 8. &lt;node-connector-port-name&gt;s3-eth1&lt;/node-connector-port-name&gt;<br/> 9. &lt;node-uni-if&gt;<br/> 10. &lt;uni-name&gt;uni1&lt;/uni-name&gt;<br/> 11. &lt;uni-node&gt;openflow:3&lt;/uni-node&gt;<br/> 12. &lt;vlan&gt;1&lt;/vlan&gt;<br/> 13. &lt;uni-description-info&gt;vr1+openflow:3+s3-eth1+vlan1&lt;/uni-description-info&gt;<br/> 14. &lt;ip-mask xmlns="urn:opendaylight:vipran:uni-bind"&gt;24&lt;/ip-mask&gt;<br/> 15. &lt;vrf xmlns="urn:opendaylight:vipran:uni-bind"&gt;vrf1&lt;/vrf&gt;<br/> 16. &lt;ip xmlns="urn:opendaylight:vipran:uni-bind"&gt;192.168.0.1&lt;/ip&gt;<br/> 17. &lt;bridge-type xmlns="urn:opendaylight:vipran:uni-bind"&gt;1toN&lt;/bridge-type&gt;<br/> 18. &lt;uni-port-name&gt;s3-eth1&lt;/uni-port-name&gt;<br/> 19. &lt;vr-id&gt;${vrname}&lt;/vr-id&gt;<br/> 20. &lt;/node-uni-if&gt;<br/> 21. &lt;/vr-node-connector&gt;<br/> 22. &lt;ip&gt;10.10.30.10&lt;/ip&gt;<br/> 23. &lt;/vr-node-a&gt;<br/> 24. &lt;vr-node-a&gt;<br/> 25. &lt;vr-node-id&gt;openflow:4&lt;/vr-node-id&gt;<br/> 26. &lt;vr-node-connector&gt;<br/> 27. &lt;node-connector-port-name&gt;s4-eth1&lt;/node-connector-port-name&gt;<br/> 28. &lt;node-uni-if&gt;<br/> 29. &lt;uni-name&gt;uni2&lt;/uni-name&gt;<br/> 30. &lt;uni-node&gt;openflow:4&lt;/uni-node&gt;<br/> 31. &lt;vlan&gt;2&lt;/vlan&gt;<br/> 32. &lt;uni-description-info&gt;vr1+openflow:4+s4-eth1+vlan2&lt;/uni-description-info&gt;<br/> 33. &lt;uni-port-name&gt;s4-eth1&lt;/uni-port-name&gt;<br/> 34. &lt;vr-id&gt;${vrname}&lt;/vr-id&gt;<br/> 35. &lt;/node-uni-if&gt;<br/> 36. &lt;/vr-node-connector&gt;<br/> 37. &lt;ip&gt;10.10.40.10&lt;/ip&gt;<br/> 38. &lt;/vr-node-a&gt;<br/> 39. &lt;vr-node-b&gt;<br/> 40. &lt;vr-node-id&gt;openflow:1&lt;/vr-node-id&gt;<br/> 41. &lt;ip&gt;10.10.10.10&lt;/ip&gt;<br/> 42. &lt;/vr-node-b&gt;<br/> 43. &lt;vr-node-b&gt;<br/> 44. &lt;vr-node-id&gt;openflow:2&lt;/vr-node-id&gt;<br/> 45. &lt;ip&gt;10.10.20.10&lt;/ip&gt;<br/> 46. &lt;/vr-node-b&gt;<br/> 47. &lt;/vr&gt;<br/> 48. &lt;/virtual-router&gt;<br/> 3\ I reboot ODL,vr-node-b data lost, vr-node-a remain.<br/> And I confirm that before the restart I were able to see both vr-a and vr-b in the data.</p> <p>1. &lt;virtual-router xmlns="urn:opendaylight:vipran:virtual-router"&gt;<br/> 2. &lt;vr&gt;<br/> 3. &lt;vr-id&gt;${vrname}&lt;/vr-id&gt;<br/> 4. &lt;vr-node-a&gt;<br/> 5. &lt;vr-node-id&gt;openflow:3&lt;/vr-node-id&gt;<br/> 6. &lt;vr-node-connector&gt;<br/> 7. &lt;node-connector-port-name&gt;s3-eth1&lt;/node-connector-port-name&gt;<br/> 8. &lt;node-uni-if&gt;<br/> 9. &lt;uni-name&gt;uni1&lt;/uni-name&gt;<br/> 10. &lt;uni-node&gt;openflow:3&lt;/uni-node&gt;<br/> 11. &lt;vlan&gt;1&lt;/vlan&gt;<br/> 12. &lt;uni-description-info&gt;vr1+openflow:3+s3-eth1+vlan1&lt;/uni-description-info&gt;<br/> 13. &lt;vrf xmlns="urn:opendaylight:vipran:uni-bind"&gt;vrf1&lt;/vrf&gt;<br/> 14. &lt;ip-mask xmlns="urn:opendaylight:vipran:uni-bind"&gt;24&lt;/ip-mask&gt;<br/> 15. &lt;bridge-type xmlns="urn:opendaylight:vipran:uni-bind"&gt;1toN&lt;/bridge-type&gt;<br/> 16. &lt;ip xmlns="urn:opendaylight:vipran:uni-bind"&gt;192.168.0.1&lt;/ip&gt;<br/> 17. &lt;uni-port-name&gt;s3-eth1&lt;/uni-port-name&gt;<br/> 18. &lt;vr-id&gt;${vrname}&lt;/vr-id&gt;<br/> 19. &lt;/node-uni-if&gt;<br/> 20. &lt;/vr-node-connector&gt;<br/> 21. &lt;/vr-node-a&gt;<br/> 22. &lt;vr-node-a&gt;<br/> 23. &lt;vr-node-id&gt;openflow:4&lt;/vr-node-id&gt;<br/> 24. &lt;vr-node-connector&gt;<br/> 25. &lt;node-connector-port-name&gt;s4-eth1&lt;/node-connector-port-name&gt;<br/> 26. &lt;node-uni-if&gt;<br/> 27. &lt;uni-name&gt;uni2&lt;/uni-name&gt;<br/> 28. &lt;uni-node&gt;openflow:4&lt;/uni-node&gt;<br/> 29. &lt;vlan&gt;2&lt;/vlan&gt;<br/> 30. &lt;uni-description-info&gt;vr1+openflow:4+s4-eth1+vlan2&lt;/uni-description-info&gt;<br/> 31. &lt;uni-port-name&gt;s4-eth1&lt;/uni-port-name&gt;<br/> 32. &lt;vr-id&gt;${vrname}&lt;/vr-id&gt;<br/> 33. &lt;/node-uni-if&gt;<br/> 34. &lt;/vr-node-connector&gt;<br/> 35. &lt;/vr-node-a&gt;<br/> 36. &lt;/vr&gt;<br/> 37. &lt;/virtual-router&gt;</p> <p>4\If I used merge method both, it will be fine. I hava test.</p> <p>Operating System: Linux<br/> Platform: PC</p> CONTROLLER-1336 Clustering: Persist data lost Bug Resolved Cannot Reproduce Tom Pantelis wuzhan Tue, 26 May 2015 07:29:58 +0000 Tue, 18 Aug 2015 10:36:39 +0000 Tue, 18 Aug 2015 10:36:39 +0000 Helium clustering 0 3 <p>Are you able to replicate this on Lithium? Or does this affects only Helium?</p> <p>(In reply to Tony Tkacik from comment #1)<br/> &gt; Are you able to replicate this on Lithium? Or does this affects only Helium?</p> <p>I only tested it on Helium sr3.<br/> Where can I get stable Lithium release?</p> <p>Need more datapoints: are both write in same transaction?<br/> Different transactions?<br/> How many writes already happened to DS?</p> <p>(In reply to Tony Tkacik from comment #3)<br/> &gt; Need more datapoints: are both write in same transaction?<br/> &gt; Different transactions?<br/> &gt; How many writes already happened to DS?</p> <p>Different transaction. <br/> Only this two transaction. And some other transactions in topology.</p> <p>Can you repro and upload the karaf.log?</p> <p>After doing that:</p> <ul class="alternate" type="square"> <li>shutdown the controller</li> <li>edit etc/opendaylight/karaf/05-clustering.xml. Find the &lt;module&gt; entry with &lt;name&gt; "distributed-config-store-module". Add the following under &lt;module&gt;</li> </ul> <p> &lt;config-properties&gt;<br/> &lt;shard-journal-recovery-log-batch-size&gt;1&lt;/shard-journal-recovery-log-batch-size&gt;<br/> &lt;config-properties/&gt; </p> <p> I assume you're writing to the config data store. If not, find "distributed-operational-store-module" and add the same except with tag &lt;operational-properties&gt;.</p> <ul class="alternate" type="square"> <li>delete the journal and snapshot directories</li> <li>restart the controller and see if it reproduces.</li> </ul> <p>Also please test this with stable/lithium to see if it repros (w/o setting shard-journal-recovery-log-batch-size to 1).</p> <p>This may not be an issue in Lithium - Tom could not reproduce. Changing milestone to Helium-4.</p> <p>To proceed with this, we need the bug reporter to test with the shard-journal-recovery-log-batch-size setting to 1 or with the latest stable/helium which has shard-journal-recovery-log-batch-size set to 1 by default.</p> <p>Also test against stable/lithium.</p> <p>I tried to reproduce by creating a yang model to mostly match the XML data from the description and doing a put and a merge similarly in separate transactions but all the data was correctly recovered on restart in both lithium and helium.</p> <p>I'll close this by the end of next week if we don't hear back from the bug reporter.</p> <p>Closing this as there was no response from the reporter.</p> Development External issue ID 3369 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02pxz: