You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/06/29 12:09:00 UTC

[jira] [Resolved] (FLINK-5254) Implement Yarn HA Services

     [ https://issues.apache.org/jira/browse/FLINK-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann resolved FLINK-5254.
----------------------------------
    Resolution: Fixed

Added via 2a7dbda79a00863a511fcf64b339770d1d00f805

> Implement Yarn HA Services
> --------------------------
>
>                 Key: FLINK-5254
>                 URL: https://issues.apache.org/jira/browse/FLINK-5254
>             Project: Flink
>          Issue Type: Sub-task
>          Components: YARN
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>              Labels: flip-6
>
> The Yarn HighAvailability Services should be 
> **Default**
>   - This option takes the YARN Application's working directory as HA storage
>   - It automatically uses that working directory for the BlobStore
>   - It creates a HDFS based "RunningJobsRegistry" (see below)
>   - ResourceManager leader election has a pre-configured leader, via the configuration, pointing to the AppMaster address.
> **ZooKeeper Based**
>   - The ZooKeeper based services use ZooKeeper for the ResourceManager and JobManager leader election. That way, they are safe against network partition scenarios that otherwise lead to "split brain" situations
> A prototype for the simple "single job" {{RunningJobsRegistry}} based on HDFS is here: https://github.com/StephanEwen/incubator-flink/commit/aaa2d7758797b2d6c9b6da42be6a5c4989468e3b



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)