You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2016/03/15 00:02:34 UTC

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

     [ https://issues.apache.org/jira/browse/YARN-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated YARN-4245:
------------------------------------------
    Summary: Clean up container-executor binary invocation interface  (was: Clean up container-executor invocation interface)

> Clean up container-executor binary 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)