hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2803) Separate client and server configs
Date Thu, 11 Aug 2011 00:27:27 GMT

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

Alejandro Abdelnur commented on MAPREDUCE-2803:

+1 as well. In addition I'd be quite happy if we change the way default client configs are
resolved, they should be resolved from a central configuration (AM?). Today changing a default
setting requires going to all client machines (from OPs perpective this is a pain)

> Separate client and server configs
> ----------------------------------
>                 Key: MAPREDUCE-2803
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2803
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Luke Lu
>             Fix For: 0.23.0
> yarn-{site,default}.xml contains many knobs none-ops users don't need to know (e.g.,
server principals and keytab locations etc.). It's confusing to users. Let's separate the
server config into separate files yarn-server-{site.default}.xml
> yarn common and client configs would remain in yarn-{site,default}.xml and YarnServerConfig
shall read both.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message