Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 6 Mar 2013 03:48:14 +0000 (UTC)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12634903.1362171729706.388975.1362541694833@arcas>
In-Reply-To: <JIRA.12634903.1362171729706@arcas>
References: <JIRA.12634903.1362171729706@arcas>
Subject: [jira] [Commented] (YARN-443) allow OS scheduling priority of NM to
 be different than the containers it launches
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594319#comment-13594319 ] 

Thomas Graves commented on YARN-443:
------------------------------------

I chose to do this in the container-executor itself and the config goes into the container-executor.cfg.  This made the change more straight forward in that we didn't have to change the args passed to container-executor.  Having the config in the container-executor.cfg also allows you to change it without restarting the NM.

new config is: process.sched.priority.  It can be set to anything that setpriority takes, including negative values since container-executor has root permissions.  If the config is left out it retains the same behavior of having priority 0.
                
> allow OS scheduling priority of NM to be different than the containers it launches
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-443
>                 URL: https://issues.apache.org/jira/browse/YARN-443
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.0.3-alpha, 0.23.6
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>         Attachments: YARN-443.patch
>
>
> It would be nice if we could have the nodemanager run at a different OS scheduling priority than the containers so that you can still communicate with the nodemanager if the containers out of control.  
> On linux we could launch the nodemanager at a higher priority, but then all the containers it launches would also be at that higher priority, so we need a way for the container executor to launch them at a lower priority.
> I'm not sure how this applies to windows if at all.

--
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