Return-Path: <issues-return-59792-archive-asf-public=cust-asf.ponee.io@flink.apache.org>
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 E0FC1200B3C
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 28 Jun 2016 11:31:58 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id DFD6C160A06; Tue, 28 Jun 2016 09:31:58 +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 3F9E8160A56
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 28 Jun 2016 11:31:58 +0200 (CEST)
Received: (qmail 23902 invoked by uid 500); 28 Jun 2016 09:31:57 -0000
Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@flink.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@flink.apache.org>
List-Post: <mailto:issues@flink.apache.org>
List-Id: <issues.flink.apache.org>
Reply-To: dev@flink.apache.org
Delivered-To: mailing list issues@flink.apache.org
Received: (qmail 23880 invoked by uid 99); 28 Jun 2016 09:31:57 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2016 09:31:57 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 0E6212C14DC
	for <issues@flink.apache.org>; Tue, 28 Jun 2016 09:31:57 +0000 (UTC)
Date: Tue, 28 Jun 2016 09:31:57 +0000 (UTC)
From: "Robert Metzger (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12982440.1466711006000.4914.1467106317055@Atlassian.JIRA>
In-Reply-To: <JIRA.12982440.1466711006000@Atlassian.JIRA>
References: <JIRA.12982440.1466711006000@Atlassian.JIRA> <JIRA.12982440.1466711006178@arcas>
Subject: [jira] [Updated] (FLINK-4114) Need a way to manage multiple named,
 long-lived jobs on a single YARN cluster in an automated manner
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 28 Jun 2016 09:31:59 -0000


     [ https://issues.apache.org/jira/browse/FLINK-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Metzger updated FLINK-4114:
----------------------------------
    Component/s: YARN Client
     Issue Type: Improvement  (was: Bug)

> Need a way to manage multiple named, long-lived jobs on a single YARN cluster in an automated manner
> ----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-4114
>                 URL: https://issues.apache.org/jira/browse/FLINK-4114
>             Project: Flink
>          Issue Type: Improvement
>          Components: YARN Client
>            Reporter: Chris Hogue
>
> We are running several Flink jobs on a single YARN cluster. Currently each Flink job is run in its own YARN session (and thus its own YARN application ID). The difficulty comes in that we want to manage each of these jobs individually by name. For example we want to start, stop, update one job without affecting others. The primary access to these jobs is via the YARN application ID, which is not meaningful to discern which flink job it is running.
> It would be nice if we had tools that would allow us to manage the flink jobs by name and have it do the right thing with the YARN session. Today we can use 'flink run' and have it start a YARN session for that job, but from that point forward we have only the YARN application ID to work with.
> As a concrete example suppose we have 2 jobs with names JobA and JobB. We'd want a way to so something like: 
> flink run <JobA jar>; flink run <JobB jar>
> We'd then want to be able to call:
> flink cancel JobA
> The cancel command would spin down the YARN session for JobA in addition to the flink job, leaving JobB running as normal. I've simplified the commands leaving out other options for illustrative purposes. And we'll want to be able to use savepoints through these steps as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)