[
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576002#comment-15576002
]
Philipp von dem Bussche commented on FLINK-2821:
------------------------------------------------
Hello [~mxm], here are my first test results.
I have built a container and am just for a first test running it with address
set to localhost and bind-address set to the actual hostname (I ended up doing
that because in Rancher it wouldn't start the container at all with address set
to the Rancher DNS name and bind-address set to the docker host name - so this
is the most simple test I could think of).
I am seeing this in the logfile of the jobmanager:
2016-10-14 17:35:22,035 ERROR org.apache.flink.runtime.jobmanager.JobManager
- Failed to run JobManager.
java.lang.Exception: Could not create JobManager actor system
at
org.apache.flink.runtime.jobmanager.JobManager$.startActorSystemAndJobManagerActors(JobManager.scala:2186)
at
org.apache.flink.runtime.jobmanager.JobManager$.runJobManager(JobManager.scala:2015)
at
org.apache.flink.runtime.jobmanager.JobManager$$anonfun$2.apply$mcV$sp(JobManager.scala:2078)
at
org.apache.flink.runtime.jobmanager.JobManager$$anonfun$2.apply(JobManager.scala:2056)
at
org.apache.flink.runtime.jobmanager.JobManager$$anonfun$2.apply(JobManager.scala:2056)
at scala.util.Try$.apply(Try.scala:161)
at
org.apache.flink.runtime.jobmanager.JobManager$.retryOnBindException(JobManager.scala:2111)
at
org.apache.flink.runtime.jobmanager.JobManager$.runJobManager(JobManager.scala:2056)
at
org.apache.flink.runtime.jobmanager.JobManager$.main(JobManager.scala:1981)
at org.apache.flink.runtime.jobmanager.JobManager.main(JobManager.scala)
Caused by: java.lang.ClassNotFoundException:
com.google.protobuf.GeneratedMessage
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
It is true that this class is not part of flink-dist_2.10-1.1.3.jar, well it is
there but as part of the shaded packages.
I compared to my running container and this class is part of the jar file with
the exact package structure in addition to the shaded structure.
bash-4.3$ unzip -l flink-dist_2.10-1.1.3.jar | grep
com.google.protobuf.GeneratedMessage
gives me a lot of these:
2006 10-14-16 14:29
org/apache/flink/hadoop/shaded/com/google/protobuf/GeneratedMessage$1.class
1203 10-14-16 14:29
org/apache/flink/hadoop/shaded/com/google/protobuf/GeneratedMessage$2.class
1665 10-14-16 14:29
org/apache/flink/hadoop/shaded/com/google/protobuf/GeneratedMessage$Builder$BuilderParentImpl.cla
whereas on the running flink jobmanager
bash-4.3$ unzip -l flink-dist_2.11-1.1.3.jar | grep
com.google.protobuf.GeneratedMessage
gives me also this:
1513 10-10-16 15:10 com/google/protobuf/GeneratedMessage$1.class
989 10-10-16 15:10 com/google/protobuf/GeneratedMessage$2.class
1296 10-10-16 15:10
com/google/protobuf/GeneratedMessage$Builder$BuilderParentImpl.class
Note that on my running containers I am using Scala 2.11.
> Change Akka configuration to allow accessing actors from different URLs
> -----------------------------------------------------------------------
>
> Key: FLINK-2821
> URL: https://issues.apache.org/jira/browse/FLINK-2821
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Reporter: Robert Metzger
> Assignee: Maximilian Michels
>
> Akka expects the actor's URL to be exactly matching.
> As pointed out here, cases where users were complaining about this:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Error-trying-to-access-JM-through-proxy-td3018.html
> - Proxy routing (as described here, send to the proxy URL, receiver
> recognizes only original URL)
> - Using hostname / IP interchangeably does not work (we solved this by
> always putting IP addresses into URLs, never hostnames)
> - Binding to multiple interfaces (any local 0.0.0.0) does not work. Still
> no solution to that (but seems not too much of a restriction)
> I am aware that this is not possible due to Akka, so it is actually not a
> Flink bug. But I think we should track the resolution of the issue here
> anyways because its affecting our user's satisfaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
