Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-8412

Re-register leader watch loop on zk reconnect

    Details

    • Type: Task
    • Status: Resolved
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: DC/OS 1.12.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Marathon 2018-28
    • Story Points:
      0
    • Build artifact:
      Marathon-v1.7.174

      Description

      In order to improve the robustness of the CuratorElectionStream implementation, we will follow the implementation in LeaderLatch and register watches anew during a reconnection event. This is to ensure that we don't get in to a state where a watch does not fire (such as a total disconnect).

      Further, we need to ignore watcher EventType None invocations, as these have to do with connection state and not the actual watcher itself. Failing to ignore this would result in the multiplication of watch loops.

        Attachments

          Activity

            People

            • Assignee:
              tharper Tim Harper
              Reporter:
              tharper Tim Harper
              Team:
              Orchestration Team
              Watchers:
              Tim Harper
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: