Allen Wittenauer updated YARN-443:
    Fix Version/s:     (was: 3.0.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
>             Fix For: 0.23.7, 2.0.4-alpha
>         Attachments: YARN-443-branch-0.23.patch, YARN-443-branch-0.23.patch, 
> YARN-443-branch-0.23.patch, YARN-443-branch-0.23.patch, 
> YARN-443-branch-2.patch, YARN-443-branch-2.patch, YARN-443-branch-2.patch, 
> YARN-443.patch, YARN-443.patch, YARN-443.patch, YARN-443.patch, 
> 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 was sent by Atlassian JIRA

Reply via email to