[
https://issues.apache.org/jira/browse/FLINK-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393601#comment-15393601
]
ASF GitHub Bot commented on FLINK-4152:
---------------------------------------
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2257
https://s3.amazonaws.com/archive.travis-ci.org/jobs/146612227/log.txt
After checking the logs again, I know why Maven isn't using the installed
`flink-runtime` artifact. It tries to download the `flink-runtime_2.11`
artifact when, in fact, it should try to download `flink-runtime-2.10`. Note,
that the build is a Scala 2.11 build but this should only set the Scala version
of dependencies but not change any Flink artifact names (we have a another
script for that). When flink-runtime is built, it is built with Scala 2.11
although named flink-runtime_2.10. Still, `flink-yarn` attempts to download
`flink-runtime_2.11`.
Trying to dig deeper, why this could be the case.
> 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)
