Uploaded image for project: 'ovsdb'
  1. ovsdb
  2. OVSDB-221

Ownership changed consistently without down any node

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Done
    • unspecified
    • None
    • None
    • Operating System: Windows
      Platform: PC

    • 4569
    • High

    Description

      I’m finding the inconsistency behaviour about ownership election in 3-node OVSDB southbound clustering.

      In 3-Node OVSDB Southbound cluster once owner node elected it should not be change until unless we goes down that node, but, in my observations find the ownership consistently changed one instance to another instance without bring down the node.

      below are my observations on 107 node.

      2015-11-02 07:23:23,428 | INFO | lt-dispatcher-21 | OvsdbConnectionManager | 174 - org.opendaylight.ovsdb.southbound-impl - 1.2.1.SNAPSHOT | handleOwnershipChanged: EntityOwnershipChanged [entity=Entity{type='ovsdb', id=/(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[

      {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1}

      ]/node/node[

      {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb:/10.106.138.116:6640}

      ]}, wasOwner=false, isOwner=true, hasOwner=true] event received for device ConnectionInfo [Remote-address=10.106.138.116, Remote-port=40335, Local-address10.106.138.107, Local-port=6640, type=PASSIVE]

      2015-11-02 08:16:48,965 | INFO | lt-dispatcher-21 | OvsdbConnectionManager | 174 - org.opendaylight.ovsdb.southbound-impl - 1.2.1.SNAPSHOT | handleOwnershipChanged: EntityOwnershipChanged [entity=Entity{type='ovsdb', id=/(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[

      {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1}

      ]/node/node[

      {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb:/10.106.138.116:6640}

      ]}, wasOwner=true, isOwner=false, hasOwner=true] event received for device ConnectionInfo [Remote-address=10.106.138.116, Remote-port=40335, Local-address10.106.138.107, Local-port=6640, type=PASSIVE]

      2015-11-02 08:17:42,892 | INFO | lt-dispatcher-16 | OvsdbConnectionManager | 174 - org.opendaylight.ovsdb.southbound-impl - 1.2.1.SNAPSHOT | handleOwnershipChanged: EntityOwnershipChanged [entity=Entity{type='ovsdb', id=/(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[

      {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1}

      ]/node/node[

      {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb:/10.106.138.116:6640}

      ]}, wasOwner=false, isOwner=true, hasOwner=true] event received for device ConnectionInfo [Remote-address=10.106.138.116, Remote-port=43804, Local-address10.106.138.107, Local-port=6640, type=PASSIVE].

      Attachments

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

        Activity

          People

            Avishnoi Anil Vishnoi
            HariPrasidh Hari Prasidh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: