[
https://issues.apache.org/jira/browse/FLINK-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shuai.xu updated FLINK-8434:
----------------------------
Description: 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. (was: 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.)
> 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
>
> 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)
