hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-443) allow OS scheduling priority of NM to be different than the containers it launches
Date Thu, 07 Mar 2013 04:26:14 GMT

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

Thomas Graves updated YARN-443:
-------------------------------

    Attachment: YARN-443.patch

I decided to go with the nice method as it should apply across all the platforms and I don't
see setting it to a negative value that useful. If its really needed you can run your nodemanager
with root permissions. 

If the windows port isn't using cygwin or you think it will cause problems let me know.  

The config in the patch is named: container-executor.os.sched.priority.adjustment

It basically does a nice -n using the config before launching the container.

Attaching the branch-0.23 patch which I've tested.  I need to create the trunk version with
the windows stuff included. 
                
> 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, YARN-443.patch, 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

Mime
View raw message