hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager
Date Tue, 10 Oct 2017 18:27:00 GMT

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

Jason Lowe edited comment on YARN-6930 at 10/10/17 6:26 PM:
------------------------------------------------------------

Thanks for the 2.8 patch!

For consistency with the trunk/branch-2 code updateEnvForWhitelistVars should not throw ContainerExecutionException.
 See DelegatingLinuxContainerRuntime#updateEnvForWhitelistVars in branch-2 for reference.
 Once that exception declaration is removed then the TestContainerLaunch changes should also
drop out of the patch.



was (Author: jlowe):
Thanks for the 2.8 patch!

I don't understand why updateEnvForWhitelistVars has been updated to throw ContainerExecutionException
when it isn't that way in trunk or branch-2.  For consistency with the trunk/branch-2 code
it should be consistent.  See DelegatingLinuxContainerRuntime#updateEnvForWhitelistVars in
branch-2 for reference.  Once that exception declaration is removed then the TestContainerLaunch
changes should also drop out of the patch.


> Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-6930
>                 URL: https://issues.apache.org/jira/browse/YARN-6930
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Shane Kumpf
>             Fix For: 2.9.0, 3.0.0-beta1
>
>         Attachments: YARN-6930.001.patch, YARN-6930.002.patch, YARN-6930.003.patch, YARN-6930.004.patch,
YARN-6930.005.patch, YARN-6930.006.patch, YARN-6930.branch-2.001.patch, YARN-6930.branch-2.002.patch,
YARN-6930.branch-2.8.001.patch, YARN-6930.branch-2.8.2.001.patch
>
>
> Today, in the java land, all LinuxContainerRuntimes are always enabled when using LinuxContainerExecutor
and the user can simply invoke anything that he/she wants - default, docker, java-sandbox.
> We should have a way for admins to explicitly enable only specific runtimes that he/she
decides for the cluster. And by default, we should have everything other than the default
one disabled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message