flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2790) Add high availability support for Yarn
Date Mon, 05 Oct 2015 00:17:26 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942870#comment-14942870
] 

ASF GitHub Bot commented on FLINK-2790:
---------------------------------------

Github user rmetzger commented on the pull request:

    https://github.com/apache/flink/pull/1213#issuecomment-145404233
  
    I've looked a bit over the code and it all looks like good changes.
    
    I've tested the code on a Hadoop 2.6.0 cluster and the YARN session was restarting properly.
But I think that's not the expected behavior.
    We actually want the TMs to stay alive and reconnect to the new AM.


> Add high availability support for Yarn
> --------------------------------------
>
>                 Key: FLINK-2790
>                 URL: https://issues.apache.org/jira/browse/FLINK-2790
>             Project: Flink
>          Issue Type: Sub-task
>          Components: JobManager, TaskManager
>            Reporter: Till Rohrmann
>             Fix For: 0.10
>
>
> Add master high availability support for Yarn. The idea is to let Yarn restart a failed
application master in a new container. For that, we set the number of application retries
to something greater than 1. 
> From version 2.4.0 onwards, it is possible to reuse already started containers for the
TaskManagers, thus, avoiding unnecessary restart delays.
> From version 2.6.0 onwards, it is possible to specify an interval in which the number
of application attempts have to be exceeded in order to fail the job. This will prevent long
running jobs from eventually depleting all available application attempts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message