hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4245) Clean up container-executor invocation interface
Date Mon, 14 Mar 2016 23:02:33 GMT

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

Vinod Kumar Vavilapalli commented on YARN-4245:
-----------------------------------------------

bq. 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.
A little late, but +10!

> 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)

Mime
View raw message