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 4812411507 for ; Fri, 6 Jun 2014 10:54:02 +0000 (UTC) Received: (qmail 18363 invoked by uid 500); 6 Jun 2014 10:54:01 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 18327 invoked by uid 500); 6 Jun 2014 10:54:01 -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 18316 invoked by uid 99); 6 Jun 2014 10:54:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2014 10:54:01 +0000 Date: Fri, 6 Jun 2014 10:54:01 +0000 (UTC) From: "Remus Rusanu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-2129) Add scheduling priority to the WindowsSecureContainerExecutor 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-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2129: ------------------------------- Attachment: YARN-2129.1.patch Take 1. This implementation, leveraging the cmd.exe start [/LOW|/HIGH| /NORMAL] /WAIT /B command line options, works fine except for the fact that, unlike *nix nice, the Windows processes do *not* inherit the priority class except for lower priorites ([/LOW|/BELOWNORMAL]). Which means that the cmd cotnainer script gets the priority boost, but not the actual java process running the task. The localizer gets the priority boost proper, but that's does not really compensate... I'll take a second stab at it and try to move the priority set to the actual java launch, around ContainerLaunch.writeLaunchEnv() and ContainerLaunch.WindowsShellScriptBuilder et all. > Add scheduling priority to the WindowsSecureContainerExecutor > ------------------------------------------------------------- > > Key: YARN-2129 > URL: https://issues.apache.org/jira/browse/YARN-2129 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager > Affects Versions: 3.0.0 > Reporter: Remus Rusanu > Assignee: Remus Rusanu > Labels: security, windows > Attachments: YARN-2129.1.patch > > > The WCE (YARN-1972) could and should honor NM_CONTAINER_EXECUTOR_SCHED_PRIORITY. -- This message was sent by Atlassian JIRA (v6.2#6252)