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

Client on a follower prefix-based shard sometimes does not reconnect when the previous leader is isolated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • None
    • None
    • clustering
    • None
    • Operating System: All
      Platform: All

    • 8605

      This has been seen on Sandbox [0] when testing for a fix [1]. Member-1 was the original leader, after isolation member-2 became the new leader, but the producer has failed on member-3.

      CONTROLLER-1704 symptom is visible from Robot and CONTROLLER-1702 symptom is visible in karaf.log [2] of member-3, but there may be more clues between 07:07:04,481 and 07:09:30,875.

      [0] https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-only-carbon/4/log.html.gz#s1-s12-t3-k2-k25-k1-k8
      [1] https://git.opendaylight.org/gerrit/#/c/58194/3
      [2] https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-only-carbon/4/odl3_karaf.log.gz

            Unassigned Unassigned
            vrpolak Vratko Polak
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: