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 2019/02/26 16:11:00 UTC
[jira] [Closed] (FLINK-2970) Yarn client cannot connect to new job
manager
[ https://issues.apache.org/jira/browse/FLINK-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-2970.
--------------------------------
Resolution: Won't Do
Closed because of inactivity.
> Yarn client cannot connect to new job manager
> ---------------------------------------------
>
> Key: FLINK-2970
> URL: https://issues.apache.org/jira/browse/FLINK-2970
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination, YARN
> Affects Versions: 0.10.0
> Reporter: Ufuk Celebi
> Priority: Major
>
> I'm running a YARN session with 2 physical nodes and 5 containers (ApplicationMaster and 4 TaskManagers). There is no Flink program submitted to the cluster.
> Running a sequence of failure operations (killing the ApplicationMaster and TaskManager containers), I sometimes get an infinite loop of
> {code}
> 15:45:29,719 WARN Remoting - Tried to associate with unreachable remote address [akka.tcp://flink@10.240.0.3:58926]. Address is now gated for 5000 ms, all messages to this address will be delivered to dead letters. Reason: Connection refused: /10.240.0.3:58926
> {code}
> I see that the ApplicationMaster container has been started though.
> I would not block the RC on this and address it for 0.10.1 or 1.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)