This could be a bug in Flink. Can you share the complete logs of the run? CC'ing Max who worked on the YARN client recently who might have an idea in which cases Flink would not set the context.
On Tue, Aug 16, 2016 at 11:00 AM, Miroslav Gajdoš <miroslav.gaj...@firma.seznam.cz> wrote: > Hi guys, > > i've run into some problems with flink/yarn. I try to deploy flink to > our cluster using /usr/lib/flink-scala2.10/bin/yarn-session.sh, but the > yarn application does not even start, it goes from accepted to > finished/failed. Yarn info on resourcemanager looks like this: > > User: wa-flink > Name: Flink session with 3 TaskManagers > Ap > plication Type: Apache Flink > Application Tags: > State: FINISHED > FinalStatus: FAILED > Started: Mon Aug 15 18:02:42 +0200 2016 > Elapsed: 16sec > Tracking URL: History > Diagnostics: Fatal error in AM: The ContainerLaunchContext was > not set. > > On dev cluster, applications deploys without problem, this happens only > in production. > > What could be wrong? > > > Thanks, > > -- > Miroslav Gajdoš > vývoj - webová analytika (Brno) > https://reporter.seznam.cz > miroslav.gaj...@firma.seznam.cz > >
