hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2976) Invalid docs for specifying yarn.nodemanager.docker-container-executor.exec-name
Date Thu, 16 Apr 2015 18:35:59 GMT

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

Hitesh Shah commented on YARN-2976:

The latter definitely makes more sense but it does not clash with the config property name.
Maybe, we can deprecate the old one in favor  of the newer config property which supports
a flexible command ( relative path, args, etc)? For the old/cuurent one, we can fix the docs
to say that it does a file exists check and does not support additional args? 

> Invalid docs for specifying yarn.nodemanager.docker-container-executor.exec-name
> --------------------------------------------------------------------------------
>                 Key: YARN-2976
>                 URL: https://issues.apache.org/jira/browse/YARN-2976
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.6.0
>            Reporter: Hitesh Shah
>            Assignee: Vijay Bhat
>            Priority: Minor
> Docs on http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/DockerContainerExecutor.html
mention setting "docker -H=tcp://" for yarn.nodemanager.docker-container-executor.exec-name.

> However, the actual implementation does a fileExists for the specified value. 
> Either the docs need to be fixed or the impl changed to allow relative paths or commands
with additional args

This message was sent by Atlassian JIRA

View raw message