Yang Wang created FLINK-19542:
---------------------------------
Summary: Implement LeaderElectionService and
LeaderRetrievalService based on Kubernetes API
Key: FLINK-19542
URL: https://issues.apache.org/jira/browse/FLINK-19542
Project: Flink
Issue Type: Sub-task
Components: Deployment / Kubernetes, Runtime / Coordination
Reporter: Yang Wang
Fix For: 1.12.0
* *_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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
