From issues-return-150963-archive-asf-public=cust-asf.ponee.io@flink.apache.org Mon Feb 5 10:29:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 9860D180647 for ; Mon, 5 Feb 2018 10:29:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 87297160C5B; Mon, 5 Feb 2018 09:29:04 +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 D0C52160C46 for ; Mon, 5 Feb 2018 10:29:03 +0100 (CET) Received: (qmail 79523 invoked by uid 500); 5 Feb 2018 09:29:03 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 79514 invoked by uid 99); 5 Feb 2018 09:29:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Feb 2018 09:29:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 892F51A0062 for ; Mon, 5 Feb 2018 09:29:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id PsgA2-VzVjc2 for ; Mon, 5 Feb 2018 09:29:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5D4B65F5FB for ; Mon, 5 Feb 2018 09:29:01 +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 9B71CE00CA for ; Mon, 5 Feb 2018 09:29:00 +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 59B0021E86 for ; Mon, 5 Feb 2018 09:29:00 +0000 (UTC) Date: Mon, 5 Feb 2018 09:29:00 +0000 (UTC) From: "Chesnay Schepler (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (FLINK-8552) CliFrontend don't exit normal after job has been submitted with 'bin/flink run some_jar_ball' MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-8552?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Chesnay Schepler closed FLINK-8552. ----------------------------------- Resolution: Not A Problem By default the client process will continue to run and print status updates= to the console. You can disable this with the {{-d}} option when submittin= g the job, i.e. {{bin/flink run -d some_jar_ball}}. For more options for su= bmitting jobs, please see https://ci.apache.org/projects/flink/flink-docs-m= aster/ops/cli.html#examples. > CliFrontend don't exit normal after job has been submitted with 'bin/flin= k run some_jar_ball' > -------------------------------------------------------------------------= -------------------- > > Key: FLINK-8552 > URL: https://issues.apache.org/jira/browse/FLINK-8552 > Project: Flink > Issue Type: Bug > Components: Client > Affects Versions: 1.4.0 > Reporter: Lynch Lee > Priority: Major > Fix For: 1.4.0 > > > I used cmd 'bin/flink run some_jar_ball' to submit my job into remote clu= ster, but I found it the java process did not exit normally while my submit= ting action is done and job status changed into RUNNING .=C2=A0 > =C2=A0 > Is this a Bug to fixed ? > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)