Re: hadoop error with flink mesos on startup

Thanks for investigating this, Jared. I would summarize it as Flink-on-Mesos cannot be used in Hadoop-free mode in Flink 1.4.0. I filed an improvement bug to support this scenario: FLINK-8247 On Tue, Dec 12, 2017 at 11:46 AM, Jared Stehler < jared.steh...@intellifylearning.com> wrote: > I had

Re: hadoop error with flink mesos on startup

I had been excluding all transitive dependencies from the lib dir; it seems to be working when I added the following deps: commons-configuration commons-configuration 1.7 commons-lang commons-lang 2.6 -- Jared Stehler Chief Architect - In

Re: hadoop error with flink mesos on startup

The class is there; this issue is a static initializer error, probably from other missing classes. I’ll try using the uber jar to see if that helps any, and will report back. I’ve included the shaded jar as a maven dependency: org.apache.flink flink-shaded-hadoop2 ${flink

Re: hadoop error with flink mesos on startup

Could you look into the flink-shaded-hadoop jar to check whether the missing class is actually contained? Where did the flink-shaded-hadoop jar come from? I'm asking because when building flink-dist from source the jar is called flink-shaded-hadoop2-uber-1.4.0.jar, which does indeed contain th

hadoop error with flink mesos on startup

After upgrading to flink 1.4.0 using the hadoop-free build option, I’m seeing the following error on startup in the app master: 2017-12-12 18:23:15.473 [main] ERROR o.a.f.m.r.clusterframework.MesosApplicationMasterRunner - Mesos JobManager initialization failed