Miklos Szegedi commented on YARN-6930:

Thank you [~shaneku...@gmail.com]. Yes, let's address the user issue in a 
different jira. Would you like to open it?
94        @Test
95        public void testIsRuntimeAllowedNotDocker() throws Exception {
98          DelegatingLinuxContainerRuntime delegatingLinuxContainerRuntime =
99              new DelegatingLinuxContainerRuntime();
100         delegatingLinuxContainerRuntime.initialize(conf);
101         assertFalse(delegatingLinuxContainerRuntime.isRuntimeAllowed(
102             dockerLinuxContainerRuntime));
103       }
This is nice, however I meant changing testIsRuntimeAllowedDefault to test that 
the default does not allow any of the other runtimes. This is what exactly 
checks what this jira is about.
Also, could you add the new config into yarn-default.xml?

> 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
>         Attachments: YARN-6930.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

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

Reply via email to