Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0BAB3200B67 for ; Tue, 16 Aug 2016 12:19:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0A354160AA8; Tue, 16 Aug 2016 10:19:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 525C7160A76 for ; Tue, 16 Aug 2016 12:19:34 +0200 (CEST) Received: (qmail 21364 invoked by uid 500); 16 Aug 2016 10:19:33 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 21351 invoked by uid 99); 16 Aug 2016 10:19:33 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Aug 2016 10:19:33 +0000 Received: from mail-oi0-f46.google.com (mail-oi0-f46.google.com [209.85.218.46]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1F0EA1A0271 for ; Tue, 16 Aug 2016 10:19:33 +0000 (UTC) Received: by mail-oi0-f46.google.com with SMTP id 4so93054602oih.2 for ; Tue, 16 Aug 2016 03:19:33 -0700 (PDT) X-Gm-Message-State: AEkoouv75coskH5JWCCy5brnZ28ijtgY6SOVSaoS3SZUeqxXLXtlvfDbc3zBVn6dk7Pr2RGPyf4SC6AFJpgalEZa X-Received: by 10.157.1.163 with SMTP id e32mr16621110ote.175.1471342772309; Tue, 16 Aug 2016 03:19:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.55.181 with HTTP; Tue, 16 Aug 2016 03:18:51 -0700 (PDT) In-Reply-To: <1471338029.4575.8.camel@firma.seznam.cz> References: <1471280335.4575.4.camel@firma.seznam.cz> <1471338029.4575.8.camel@firma.seznam.cz> From: Ufuk Celebi Date: Tue, 16 Aug 2016 12:18:51 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: flink on yarn - Fatal error in AM: The ContainerLaunchContext was not set To: user@flink.apache.org Cc: mxm@apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable archived-at: Tue, 16 Aug 2016 10:19:35 -0000 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=C5=A1 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=C5=A1 > v=C3=BDvoj - webov=C3=A1 analytika (Brno) > https://reporter.seznam.cz > miroslav.gajdos@firma.seznam.cz > >