Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-6078

ZooKeeper based high availability services should not close the underlying CuratorFramework

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1.3.0
    • Labels:
      None

      Description

      ZooKeeper based high availability tools like ZooKeeperLeaderRetrievalService and ZooKeeperLeaderElectionService expect that every instance of the services have a dedicated CuratorFramework instance assigned. Thus, they also close this CuratorFramework when the service is closed. This does not play well along with the newly introduced HighAvailabilityServices which caches a single CuratorFramework and shares it among all created services. In order to make it work properly together I propose to change the behaviour such that we no longer close the CuratorFramework clients in the ZooKeeper based services.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                till.rohrmann Till Rohrmann
                Reporter:
                till.rohrmann Till Rohrmann
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: