Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-7623

Device events are not replicated to other instances

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.13.0
    • Fix Version/s: 1.13.0
    • Component/s: None
    • Labels:
    • Environment:

      7be4e67f7b24c20dc91ad29396ad9e5648e817b5

    • Story Points:
      3
    • Epic Link:
    • Sprint:
      N Sprint #6 - QA

      Description

      After patch 16278, DEVICE_ADDED events are no longer replicated to all instances in the cluster once they are seen by one of the instances which causes a large increase in switch-up latency. Specifically, without the replication method, instances need to wait for gossip to synchronize on DEVICE events which takes seconds to finish.

      And it seems the reason that the replication method is not working is because mastership assignment is not finished yet when the device store created a DEVICE event. So the following code is not executed

      if (isMaster) {
          log.info("Notifying peers of a device update topology event for providerId: {} and deviceId: {}",
          providerId, deviceId);
          notifyPeers(new InternalDeviceEvent(providerId, deviceId, mergedDesc));
      }
      

        Attachments

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

          Activity

            People

            Assignee:
            tom Thomas Vachuska
            Reporter:
            You You Wang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: