[
https://issues.apache.org/jira/browse/FLINK-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387352#comment-15387352
]
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_r71664748
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/clusterframework/FlinkResourceManager.java
---
@@ -113,7 +111,8 @@
/** The service to find the right leader JobManager (to support high
availability) */
private final LeaderRetrievalService leaderRetriever;
- /** The currently registered resources */
+ /** The resources which have been registered at the ResourceManager.
This indicates the set
+ * of containers where a TaskManager has been started and registered at
a JobManager. */
--- End diff --
Yes and we should change the comment to not state that they have been
registered at the JobManager because currently they are registered at the
ResourceManager before JobManager 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)
