From issues-return-198930-archive-asf-public=cust-asf.ponee.io@flink.apache.org Thu Nov 1 17:48:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4EF3A180789 for ; Thu, 1 Nov 2018 17:48:06 +0100 (CET) Received: (qmail 90246 invoked by uid 500); 1 Nov 2018 16:48:04 -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 90166 invoked by uid 99); 1 Nov 2018 16:48:04 -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; Thu, 01 Nov 2018 16:48:04 +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 E09EA1A502E for ; Thu, 1 Nov 2018 16:48:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id kYBYB_1pra-1 for ; Thu, 1 Nov 2018 16:48:03 +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 AE7495F673 for ; Thu, 1 Nov 2018 16:48:02 +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 C0949E0D9F for ; Thu, 1 Nov 2018 16:48:01 +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 155D927779 for ; Thu, 1 Nov 2018 16:48:01 +0000 (UTC) Date: Thu, 1 Nov 2018 16:48:01 +0000 (UTC) From: "Till Rohrmann (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLINK-10743) Use 0 processExitCode for ApplicationStatus.CANCELED 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-10743?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Rohrmann updated FLINK-10743: ---------------------------------- Fix Version/s: 1.7.0 > Use 0 processExitCode for ApplicationStatus.CANCELED > ---------------------------------------------------- > > Key: FLINK-10743 > URL: https://issues.apache.org/jira/browse/FLINK-10743 > Project: Flink > Issue Type: Bug > Components: Cluster Management, Kubernetes, Mesos, YARN > Affects Versions: 1.6.3, 1.7.0 > Reporter: Ufuk Celebi > Assignee: Ufuk Celebi > Priority: Minor > Fix For: 1.7.0 > > > {{org.apache.flink.runtime.clusterframework.ApplicationStatus}} is used t= o map {{org.apache.flink.runtime.jobgraph.JobStatus}} to a process exit cod= e. > We currently map {{ApplicationStatus.CANCELED}} to a non-zero exit code (= {{1444}}). Since cancellation is a user-triggered operation I would conside= r this to be a successful exit and map it to exit code {{0}}. > Our current behavior results in applications running via the {{Standalone= JobClusterEntryPoint}} and Kubernetes pods as documented in [flink-containe= r|https://github.com/apache/flink/tree/master/flink-container/kubernetes] t= o be immediately restarted when=C2=A0cancelled. This only leaves the option= of killing the respective job cluster master container. > The {{ApplicationStatus}} is also used in the YARN and Mesos clients, but= I'm not familiar with that part of the code base and can't asses how=C2=A0= changing the exit code would affect these clients. A quick usage scan for {= {ApplicationStatus.CANCELED}}=C2=A0did not surface any problematic usages t= hough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)