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 D568D200BBD for ; Tue, 8 Nov 2016 18:34:59 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D42C5160B0C; Tue, 8 Nov 2016 17:34:59 +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 4CB0E160AD0 for ; Tue, 8 Nov 2016 18:34:59 +0100 (CET) Received: (qmail 93529 invoked by uid 500); 8 Nov 2016 17:34:58 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 93495 invoked by uid 99); 8 Nov 2016 17:34:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Nov 2016 17:34:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 587902C0276 for ; Tue, 8 Nov 2016 17:34:58 +0000 (UTC) Date: Tue, 8 Nov 2016 17:34:58 +0000 (UTC) From: "Billie Rinaldi (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-5855) DELETE call sometimes returns success when app is not deleted MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 08 Nov 2016 17:35:00 -0000 Billie Rinaldi created YARN-5855: ------------------------------------ Summary: DELETE call sometimes returns success when app is not deleted Key: YARN-5855 URL: https://issues.apache.org/jira/browse/YARN-5855 Project: Hadoop YARN Issue Type: Sub-task Reporter: Billie Rinaldi Assignee: Gour Saha Looking into this issue with [~gsaha], we noticed that multiple things can contribute to an app continuing to run after a DELETE call, which consists of a stop and a destroy operation. One problem is that the stop call is asynchronous unless a force flag is set. Without the force flag, a message is sent to the AM and success is returned, and with the flag yarnClient.killRunningApplication is called. (There is also an option to wait for a fixed amount of time for the app to stop before returning, but DELETE is not setting this option and force is preferable in this case.) The other issue is that the destroy operation is attempted in a loop, but if the number of retries is exceeded the call returns a 204 response. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org