[
https://issues.apache.org/jira/browse/FLINK-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384234#comment-15384234
]
ASF GitHub Bot commented on FLINK-4152:
---------------------------------------
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/2257#discussion_r71350758
--- Diff:
flink-yarn/src/main/java/org/apache/flink/yarn/YarnFlinkResourceManager.java ---
@@ -78,6 +79,9 @@
/** The containers where a TaskManager is starting and we are waiting
for it to register */
private final Map<ResourceID, YarnContainerInLaunch> containersInLaunch;
+ /** The container where a TaskManager has been started and is running
in */
+ private final Map<ResourceID, Container> containersLaunched;
--- End diff --
>You tell me, since you've authored this component.
I think there is a misunderstanding. I did author this component but it is
not mine. I know you spend some time working on this and I just want to
understand your motives. I thought actually you had tried this fix since you
mentioned it in the JIRA.
I think clearing the list is simply a bug and artifact of an old code
design where the ResourceManager would be the central instance for TaskManager
registration.
> TaskManager registration exponential backoff doesn't work
> ---------------------------------------------------------
>
> Key: FLINK-4152
> URL: https://issues.apache.org/jira/browse/FLINK-4152
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination, TaskManager, YARN Client
> Reporter: Robert Metzger
> Assignee: Till Rohrmann
> Attachments: logs.tgz
>
>
> While testing Flink 1.1 I've found that the TaskManagers are logging many
> messages when registering at the JobManager.
> This is the log file:
> https://gist.github.com/rmetzger/0cebe0419cdef4507b1e8a42e33ef294
> Its logging more than 3000 messages in less than a minute. I don't think that
> this is the expected behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
