You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/17 13:35:00 UTC

[jira] [Commented] (FLINK-8434) The new yarn resource manager should take over the running task managers after failover

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

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

Github user GJL commented on the issue:

    https://github.com/apache/flink/pull/5297
  
    Thank you for your contribution  @shuai-xu. Unfortunately this is a duplicate of FLINK-7805. Can you close this PR?


> The new yarn resource manager should take over the running task managers after failover
> ---------------------------------------------------------------------------------------
>
>                 Key: FLINK-8434
>                 URL: https://issues.apache.org/jira/browse/FLINK-8434
>             Project: Flink
>          Issue Type: Bug
>          Components: Cluster Management
>    Affects Versions: 1.5.0
>            Reporter: shuai.xu
>            Assignee: shuai.xu
>            Priority: Major
>              Labels: flip-6
>             Fix For: 1.5.0
>
>
> The app master which container the job master and yarn resource manager may failover during running on yarn. The new resource manager should take over the running task managers after started. But now the YarnResourceManager does not record the running container to workerNodeMap, so when task managers register to it, it will reject them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)