Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6082E18783 for ; Fri, 20 Nov 2015 16:19:12 +0000 (UTC) Received: (qmail 59520 invoked by uid 500); 20 Nov 2015 16:19:11 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 59401 invoked by uid 500); 20 Nov 2015 16:19:11 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 59141 invoked by uid 99); 20 Nov 2015 16:19:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2015 16:19:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 126E62C1F70 for ; Fri, 20 Nov 2015 16:19:11 +0000 (UTC) Date: Fri, 20 Nov 2015 16:19:11 +0000 (UTC) From: "Jaromir Vanek (JIRA)" To: yarn-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-4377) Container process not killed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jaromir Vanek created YARN-4377: ----------------------------------- Summary: Container process not killed Key: YARN-4377 URL: https://issues.apache.org/jira/browse/YARN-4377 Project: Hadoop YARN Issue Type: Bug Components: nodemanager Affects Versions: 2.6.0 Environment: Debian linux Reporter: Jaromir Vanek Priority: Critical It seems my processes in containers are not killed when the whole job is killed. Containers will hang in {{KILLING}} state until forever. The root of this problem is that signals sent to the container process are sent with wrong user permissions. >From the nodemanager log: {quote} 2015-11-20 15:38:22,063 DEBUG org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch: Got pid 20748 for container container_1443786884805_2298_01_000003 2015-11-20 15:38:22,063 DEBUG org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch: Sending signal to pid 20748 as user _submitter_ for container container_1443786884805_2298_01_000003 2015-11-20 15:38:22,063 DEBUG org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: Sending signal 15 to pid 20748 as user _submitter_ 2015-11-20 15:38:22,069 DEBUG org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch: Sent signal SIGTERM to pid 20748 as user _submitter_ for container container_1443786884805_2298_01_000003, result=failed 2015-11-20 15:38:22,319 DEBUG org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: Sending signal 9 to pid 20748 as user _submitter_ {quote} {{SIGTERM}} and following {{SIGKILL}} signals are sent with the *submitter* user permissions, but the container process is running under *yarn* user by default (when using {{DefaultContainerExecutor}} which is true in my case}}. The result is that signals are ignored and container will run forever. Am I doing something wrong or is it a bug? -- This message was sent by Atlassian JIRA (v6.3.4#6332)