You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Remus Rusanu (JIRA)" <ji...@apache.org> on 2014/06/06 12:54:01 UTC

[jira] [Updated] (YARN-2129) Add scheduling priority to the WindowsSecureContainerExecutor

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