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 9927B200C2F for ; Mon, 6 Mar 2017 22:46:39 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 97A9F160B76; Mon, 6 Mar 2017 21:46:39 +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 E3547160B66 for ; Mon, 6 Mar 2017 22:46:38 +0100 (CET) Received: (qmail 71827 invoked by uid 500); 6 Mar 2017 21:46:38 -0000 Mailing-List: contact commits-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list commits@beam.apache.org Received: (qmail 71818 invoked by uid 99); 6 Mar 2017 21:46:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2017 21:46:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B8156C124F for ; Mon, 6 Mar 2017 21:46:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id gE2lSogeWb11 for ; Mon, 6 Mar 2017 21:46:37 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F11C45F36B for ; Mon, 6 Mar 2017 21:46:36 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 23CCFE05BB for ; Mon, 6 Mar 2017 21:46:33 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id D07BD2416A for ; Mon, 6 Mar 2017 21:46:32 +0000 (UTC) Date: Mon, 6 Mar 2017 21:46:32 +0000 (UTC) From: "Davor Bonaci (JIRA)" To: commits@beam.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (BEAM-1631) Flink runner: submit job to a Flink-on-YARN cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 06 Mar 2017 21:46:39 -0000 Davor Bonaci created BEAM-1631: ---------------------------------- Summary: Flink runner: submit job to a Flink-on-YARN cluster Key: BEAM-1631 URL: https://issues.apache.org/jira/browse/BEAM-1631 Project: Beam Issue Type: New Feature Components: runner-flink Reporter: Davor Bonaci Assignee: Aljoscha Krettek As far as I understand, running Beam pipelines on a Flink cluster can be done in two ways: * Run directly with a Flink runner, and specifying {{--flinkMaster}} pipeline option via, say, {{mvn exec}}. * Produce a bundled JAR, and use {{bin/flink}} to submit the same pipeline. These two ways are equivalent, and work well on a standalone Flink cluster. Submitting to a Flink-on-YARN is more complicated. You can still produce a bundled JAR, and use {{bin/flink -yid }} to submit such a job. However, that seems impossible with a Flink runner directly. If so, we should add the ability to the Flink runner to submit a job to a Flink-on-YARN cluster directly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)