Uploaded image for project: 'controller'
  1. controller
  2. CONTROLLER-1336

Clustering: Persist data lost

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Cannot Reproduce
    • Helium
    • None
    • clustering
    • None
    • Operating System: Linux
      Platform: PC

    • 3369

    Description

      I used one node cluster.
      1\First, I wrote data on path:
      InstanceIdentifier.builder(VirtualRouter.class)
      .child(Vr.class, new VrKey(vrId)).toInstance();
      I used put method. Restconf result is
      1. <virtual-router xmlns="urn:opendaylight:vipran:virtual-router">
      2. <vr>
      3. <vr-id>${vrname}</vr-id>
      4. <vr-node-a>
      5. <vr-node-id>openflow:3</vr-node-id>
      <ip>10.10.30.10</ip>
      6. </vr-node-a>
      7. <vr-node-a>
      8. <vr-node-id>openflow:4</vr-node-id>
      <ip>10.10.40.10</ip>
      9. </vr-node-a>
      10. <topology-id>${vrname}</topology-id>
      11. <vr-node-b>
      12. <vr-node-id>openflow:1</vr-node-id>
      <ip>10.10.10.10</ip>
      13. </vr-node-b>
      14. <vr-node-b>
      15. <vr-node-id>openflow:2</vr-node-id>
      <ip>10.10.20.10</ip>
      16. </vr-node-b>
      17. </vr>
      18. </virtual-router>

      2\Then, I wrote data on path:
      InstanceIdentifier.builder(VirtualRouter.class)
      .child(Vr.class, new VrKey(uniIf.getVrId()))
      .child(VrNodeA.class, new VrNodeAKey(uniIf.getUniNode()))
      .child(VrNodeConnector.class, new VrNodeConnectorKey(uniIf.getUniPortName()))
      .child(NodeUniIf.class, new NodeUniIfKey(uniIf.getUniName())).toInstance();
      I used merge method. Restconf result is
      1. <virtual-router xmlns="urn:opendaylight:vipran:virtual-router">
      2. <vr>
      3. <vr-id>${vrname}</vr-id>
      4. <topology-id>${vrname}</topology-id>
      5. <vr-node-a>
      6. <vr-node-id>openflow:3</vr-node-id>
      7. <vr-node-connector>
      8. <node-connector-port-name>s3-eth1</node-connector-port-name>
      9. <node-uni-if>
      10. <uni-name>uni1</uni-name>
      11. <uni-node>openflow:3</uni-node>
      12. <vlan>1</vlan>
      13. <uni-description-info>vr1+openflow:3+s3-eth1+vlan1</uni-description-info>
      14. <ip-mask xmlns="urn:opendaylight:vipran:uni-bind">24</ip-mask>
      15. <vrf xmlns="urn:opendaylight:vipran:uni-bind">vrf1</vrf>
      16. <ip xmlns="urn:opendaylight:vipran:uni-bind">192.168.0.1</ip>
      17. <bridge-type xmlns="urn:opendaylight:vipran:uni-bind">1toN</bridge-type>
      18. <uni-port-name>s3-eth1</uni-port-name>
      19. <vr-id>${vrname}</vr-id>
      20. </node-uni-if>
      21. </vr-node-connector>
      22. <ip>10.10.30.10</ip>
      23. </vr-node-a>
      24. <vr-node-a>
      25. <vr-node-id>openflow:4</vr-node-id>
      26. <vr-node-connector>
      27. <node-connector-port-name>s4-eth1</node-connector-port-name>
      28. <node-uni-if>
      29. <uni-name>uni2</uni-name>
      30. <uni-node>openflow:4</uni-node>
      31. <vlan>2</vlan>
      32. <uni-description-info>vr1+openflow:4+s4-eth1+vlan2</uni-description-info>
      33. <uni-port-name>s4-eth1</uni-port-name>
      34. <vr-id>${vrname}</vr-id>
      35. </node-uni-if>
      36. </vr-node-connector>
      37. <ip>10.10.40.10</ip>
      38. </vr-node-a>
      39. <vr-node-b>
      40. <vr-node-id>openflow:1</vr-node-id>
      41. <ip>10.10.10.10</ip>
      42. </vr-node-b>
      43. <vr-node-b>
      44. <vr-node-id>openflow:2</vr-node-id>
      45. <ip>10.10.20.10</ip>
      46. </vr-node-b>
      47. </vr>
      48. </virtual-router>
      3\ I reboot ODL,vr-node-b data lost, vr-node-a remain.
      And I confirm that before the restart I were able to see both vr-a and vr-b in the data.

      1. <virtual-router xmlns="urn:opendaylight:vipran:virtual-router">
      2. <vr>
      3. <vr-id>${vrname}</vr-id>
      4. <vr-node-a>
      5. <vr-node-id>openflow:3</vr-node-id>
      6. <vr-node-connector>
      7. <node-connector-port-name>s3-eth1</node-connector-port-name>
      8. <node-uni-if>
      9. <uni-name>uni1</uni-name>
      10. <uni-node>openflow:3</uni-node>
      11. <vlan>1</vlan>
      12. <uni-description-info>vr1+openflow:3+s3-eth1+vlan1</uni-description-info>
      13. <vrf xmlns="urn:opendaylight:vipran:uni-bind">vrf1</vrf>
      14. <ip-mask xmlns="urn:opendaylight:vipran:uni-bind">24</ip-mask>
      15. <bridge-type xmlns="urn:opendaylight:vipran:uni-bind">1toN</bridge-type>
      16. <ip xmlns="urn:opendaylight:vipran:uni-bind">192.168.0.1</ip>
      17. <uni-port-name>s3-eth1</uni-port-name>
      18. <vr-id>${vrname}</vr-id>
      19. </node-uni-if>
      20. </vr-node-connector>
      21. </vr-node-a>
      22. <vr-node-a>
      23. <vr-node-id>openflow:4</vr-node-id>
      24. <vr-node-connector>
      25. <node-connector-port-name>s4-eth1</node-connector-port-name>
      26. <node-uni-if>
      27. <uni-name>uni2</uni-name>
      28. <uni-node>openflow:4</uni-node>
      29. <vlan>2</vlan>
      30. <uni-description-info>vr1+openflow:4+s4-eth1+vlan2</uni-description-info>
      31. <uni-port-name>s4-eth1</uni-port-name>
      32. <vr-id>${vrname}</vr-id>
      33. </node-uni-if>
      34. </vr-node-connector>
      35. </vr-node-a>
      36. </vr>
      37. </virtual-router>

      4\If I used merge method both, it will be fine. I hava test.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            tpantelis Tom Pantelis
            zhan_wu2001@aliyun.com wuzhan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: