You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/01/16 13:24:27 UTC
[jira] [Commented] (FLINK-5496) ClassCastException when using Mesos
HA mode
[ https://issues.apache.org/jira/browse/FLINK-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823960#comment-15823960 ]
Till Rohrmann commented on FLINK-5496:
--------------------------------------
The root cause seems to be that multiple modules: {{flink-runtime}}, {{flink-mesos}} and {{flink-kafka-0.8}} relocate the curator dependency with different relocation patterns. I propose to introduce a common relocation pattern for the curator dependency in the parent pom.xml file.
> ClassCastException when using Mesos HA mode
> -------------------------------------------
>
> Key: FLINK-5496
> URL: https://issues.apache.org/jira/browse/FLINK-5496
> Project: Flink
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Critical
> Fix For: 1.2.0, 1.3.0
>
>
> When using the Mesos' HA mode, one cannot start the Mesos appmaster, because the following class cast exception occurs:
> {code}
> java.lang.ClassCastException: org.apache.flink.shaded.org.apache.curator.framework.imps.CuratorFrameworkImpl cannot be cast to org.apache.flink.mesos.shaded.org.apache.curator.framework.CuratorFramework
> at org.apache.flink.mesos.util.ZooKeeperUtils.startCuratorFramework(ZooKeeperUtils.java:38)
> at org.apache.flink.mesos.runtime.clusterframework.MesosApplicationMasterRunner.createWorkerStore(MesosApplicationMasterRunner.java:510)
> at org.apache.flink.mesos.runtime.clusterframework.MesosApplicationMasterRunner.runPrivileged(MesosApplicationMasterRunner.java:320)
> at org.apache.flink.mesos.runtime.clusterframework.MesosApplicationMasterRunner$1.call(MesosApplicationMasterRunner.java:178)
> at org.apache.flink.mesos.runtime.clusterframework.MesosApplicationMasterRunner$1.call(MesosApplicationMasterRunner.java:175)
> at org.apache.flink.runtime.security.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:29)
> at org.apache.flink.mesos.runtime.clusterframework.MesosApplicationMasterRunner.run(MesosApplicationMasterRunner.java:175)
> at org.apache.flink.mesos.runtime.clusterframework.MesosApplicationMasterRunner.main(MesosApplicationMasterRunner.java:135)
> {code}
> It seems as if the {{flink-mesos}} module relocates the curator dependency in another namespace than {{flink-runtime}}. Not sure why this is done.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)