Shane Kumpf commented on YARN-6930:

Thanks [~miklos.szeg...@cloudera.com] and [~ebadger] for the feedback. I have 
attached a new patch that addresses your comments and the issues reported by 
the precommit job.

Should we set runtime = null if the runtime isn't allowed, just in case someone 
catches the ContainerExecutionException somewhere up the line?
I don't believe this is necessary given the scope of runtime, so I've left this 
change out. Let me know if I'm missing something here.

I'm still looking into the c-e test failure, but it may be unrelated.

> 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, YARN-6930.002.patch, 
> YARN-6930.003.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