[
https://issues.apache.org/jira/browse/FLINK-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-19543.
---------------------------------
Resolution: Fixed
Fixed via
d1f186542c
86d20190b4
3dda515d27
90df9303f2
c3a6b51459
8b4f28b334
847f3bb0b3
5f7e0dc965
> Implement RunningJobsRegistry, JobGraphStore based on Kubernetes API
> --------------------------------------------------------------------
>
> Key: FLINK-19543
> URL: https://issues.apache.org/jira/browse/FLINK-19543
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes, Runtime / Coordination
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> * *_RunningJobsRegistry_*
> * Registry for the running jobs. All the jobs in the registry will be
> recovered when JobManager failover.
> * *_JobGraphStore_*
> * JobGraph instances for running JobManagers. Note that only the meta
> information(aka location reference, DFS path) will be stored in the
> Zookeeper/ConfigMap. The real data is stored on the DFS.
> Each component(Dispatcher, ResourceManager, JobManager, RestEndpoint) will
> have a dedicated ConfigMap. All the HA information relevant for a specific
> component will be stored in a single ConfigMap. So the Dispatcher's ConfigMap
> would then contain the current leader, the running jobs and the pointers to
> the persisted JobGraphs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
