[
https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197107#comment-16197107
]
Shane Kumpf commented on YARN-6930:
-----------------------------------
The findbugs warning is unrelated to this patch. YARN-7034 addressed the
warning for trunk and branch-2, but it appears this was missed in the
branch-2.8 patch. I'll open a new JIRA to address this in branch-2.8 and
branch-2.8.2.
> 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.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
