[
https://issues.apache.org/jira/browse/FLINK-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393730#comment-15393730
]
ASF GitHub Bot commented on FLINK-4152:
---------------------------------------
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2257
Found the culprit. We must not use the `scala.binary.version` property in
flink artifact names. The property is only for switching Scala dependencies. It
is not resolved by Maven in artifact names during deployment which would give
us artifact names of the form `flink-runtime_${scala.binary.version}`. The
problem is that we set the property in the root pom which can only be deployed
one time. Otherwise all artifacts would depend on Scala...a bit nasty.
The build failures occurred because Maven tried to use the
`flink-runtime_2.11` dependency instead of `flink-runtime_2.10` (which is in
fact the Scala 2.11 version if you use `-Dscala-2.11`). `flink-runtime_2.11`
hadn't been installed previously, causing Maven to download it from the
snapshot repository...
I think we're done with this PR after this. I'm going to run the changes on
Travis and will merge to the master then.
> 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)
