[
https://issues.apache.org/jira/browse/FLINK-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382487#comment-15382487
]
ASF GitHub Bot commented on FLINK-4152:
---------------------------------------
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2257
It was just a surprise to me that we're breaking the original
ResourceManager role. If the ResourceManager doesn't get eventually notified
about new TaskManagers, then it is not guaranteed anymore that the
ResourceManager can fulfill pool size requests. The JobManager will have to
deal with the pool size and the logic to ensure enough resources are available.
Thus, the JobManager will be more concerned with managing resources.
> 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)
