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] [Updated] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager
Date Mon, 09 Oct 2017 14:52:00 GMT

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

Jason Lowe updated YARN-6930:
-----------------------------
    Target Version/s: 2.8.2
       Fix Version/s:     (was: 2.8.2)

Thanks for the patch!

In the future, please do not set the Fix Version/s field to indicate where a patch should
be targeted.  That field should only be updated by the committer when the changes are committed.
 The Target Version/s field is for specifying where changes should/need to go, and the Fix
Version/s field tracks where changes have been committed.  Otherwise we can't tell from the
JIRA whether this has or has not been fixed in those versions.

The 2.8.2 patch looks OK to me, but in order for this to go into branch-2.8.2 it first needs
to go into branch-2.8.  However the 2.8.2 patch does not apply to branch-2.8.  Could you please
supply a patch for branch-2.8 as well?


> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message