Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 4 Nov 2011 20:57:51 +0000 (UTC)
From: "Robert Joseph Evans (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1493054591.1079.1320440271574.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1619105360.650.1320433791683.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3359) Yarn clients / AM should be
 able to provide config options to the RM / NM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans commented on MAPREDUCE-3359:
------------------------------------------------

I think that protocol buffers offers some benefits over generic key/value pairs.  It includes types, even complex types that are very difficult to do with just key/value pairs.  It helps to ensure binary compatibility and has default values built in.  Yes if we do remove a config value that number must remain reserved for eternity and if we add in a new config it must be added to the proto file. Keeping a number reserved is not that painful and after having gone through the process of trying to document/clean up all of the yarn config options that where not published in the yarn-defaults.xml I am 100% in favor of forcing a single machine readable location for parameter values.
                
> Yarn clients / AM should be able to provide config options to the RM / NM
> -------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3359
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3359
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Siddharth Seth
>            Assignee: Robert Joseph Evans
>         Attachments: MR-3359.txt
>
>
> The RM and NM do not read a job's configuration. Clients / AMs should however be able to configure certain parameters for the RM/NM on a per app basis - like the Log Retention policy, token cancellation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira