Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 792081985A for ; Mon, 14 Mar 2016 23:02:34 +0000 (UTC) Received: (qmail 61846 invoked by uid 500); 14 Mar 2016 23:02:34 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 61763 invoked by uid 500); 14 Mar 2016 23:02:34 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 61482 invoked by uid 99); 14 Mar 2016 23:02:34 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Mar 2016 23:02:34 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 007DB2C1F68 for ; Mon, 14 Mar 2016 23:02:34 +0000 (UTC) Date: Mon, 14 Mar 2016 23:02:34 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4245) Clean up container-executor binary invocation interface MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)