Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-12884 FLIP-144: Native Kubernetes HA Service
  3. FLINK-19542

Implement LeaderElectionService and LeaderRetrievalService based on Kubernetes API

    XMLWordPrintableJSON

Details

    Description

      • LeaderElectionService
      • Contends for the leadership of a service in JobManager. There are four components in a JobManager instance that use LeaderElectionService: ResourceManager, Dispatcher, JobManager, RestEndpoint(aka WebMonitor). 
      • Once the leader election is finished, the active leader addresses will be stored in the ConfigMap so that other components could retrieve successfully. 
      • LeaderRetrievalService
      • Used by Client to get the RestEndpoint address for the job submission.
      • Used by JobManager to get the ResourceManager address for registration.
      • Used by TaskManagers to retrieve addresses of the corresponding LeaderElectionService(e.g. JobManager address, ResourceManager address) for registration and offering slots

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue FLINK-30765 LeaderElectionService.stop should always call revokeLeadership

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #13644

          Activity

            People

              wangyang0918 Yang Wang
              wangyang0918 Yang Wang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: