hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2803) Separate client and server configs
Date Wed, 10 Aug 2011 23:24:29 GMT

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

Luke Lu commented on MAPREDUCE-2803:
------------------------------------

Currently client reads yarn-*.xml via YarnRunner to get RM RPC address and web UI address
and other user options (client retry, timeout etc. that could be added later). Whether the
client config should be called yarn-{site,default}.xml or yarn-client-{site,default}.xml is
something I don't particular care about. Having a simpler client config is much more user
friendly.

Having separate client and server config can actually simplify/clarify deployment: client
configs are deployed at gateways and doesn't need update when server knobs are being tuned.

> 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

        

Mime
View raw message