hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-443) allow OS scheduling priority of NM to be different than the containers it launches
Date Fri, 01 Mar 2013 21:41:12 GMT

     [ https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bikas Saha updated YARN-443:
----------------------------

    Summary: allow OS scheduling priority of NM to be different than the containers it launches
 (was: allow OS scheduling priority of NM to be different then the containers it launches)
    
> 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
>
> It would be nice if we could have the nodemanager run at a different OS scheduling priority
then 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

Mime
View raw message