Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 91904F9B3 for ; Thu, 21 Mar 2013 19:23:17 +0000 (UTC) Received: (qmail 57926 invoked by uid 500); 21 Mar 2013 19:23:15 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 57885 invoked by uid 500); 21 Mar 2013 19:23:15 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 57797 invoked by uid 99); 21 Mar 2013 19:23:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Mar 2013 19:23:15 +0000 Date: Thu, 21 Mar 2013 19:23:15 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-493) NodeManager job control logic flaws on Windows MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-493: ------------------------------- Description: Both product and test code contain some platform-specific assumptions, such as availability of bash for executing a command in a container and signals to check existence of a process and terminate it. (was: The tests contain some platform-specific assumptions, such as availability of bash for executing a command in a container and signals to check existence of a process and terminate it.) Summary: NodeManager job control logic flaws on Windows (was: TestContainerManager fails on Windows) I'm expanding the scope of this jira to cover some flaws I've discovered in NodeManager's job control logic on Windows: # Windows was erroneously flagged as supporting setsid, which caused prepending of a '-' character to the job ID passed to winutils. # Exit code from job terminated by winutils task kill differed from expectations in YARN Java code, so that it couldn't tell the difference between a killed container vs. a container that had exited with failure. # Multiple tests were relying on bash scripts and signals for launching and controlling containers. I have a patch in progress. With the expanded scope, the patch will fix the following tests on Windows: {{TestContainerLaunch}}, {{TestContainerManager}}, and {{TestNodeManagerShutdown}}. > NodeManager job control logic flaws on Windows > ---------------------------------------------- > > Key: YARN-493 > URL: https://issues.apache.org/jira/browse/YARN-493 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Reporter: Chris Nauroth > Assignee: Chris Nauroth > Fix For: 3.0.0 > > > Both product and test code contain some platform-specific assumptions, such as availability of bash for executing a command in a container and signals to check existence of a process and terminate it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira