[jira] [Commented] (YARN-4245) Clean up container-executor invocation interface

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on YARN-4245:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #9432 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9432/])
YARN-4245. Generalize config file handling in container-executor. (vvasudev: rev 8ed2e060e80c0def3fcb7604e0bd27c1c24d291e)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/test/test-container-executor.c
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.c
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.h
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.c
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/main.c
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/configuration.h


> Clean up container-executor invocation interface
> ------------------------------------------------
>
>                 Key: YARN-4245
>                 URL: https://issues.apache.org/jira/browse/YARN-4245
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 3.0.0, 2.8.0
>            Reporter: Sidharta Seethana
>            Assignee: Sidharta Seethana
>
> The current container-executor invocation interface (especially for launch container) is cumbersome to use . Launching a container now requires 13-15 arguments.  This becomes especially problematic when additional, potentially optional, arguments are required. We need a better mechanism to deal with this. One such mechanism could be to handle this could be to use a file containing key/value pairs (similar to container-executor.cfg) corresponding to the arguments each invocation needs. Such a mechanism would make it easier to add new optional arguments to container-executor and better manage existing ones. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)