[
https://issues.apache.org/jira/browse/MAPREDUCE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089636#comment-13089636
]
Robert Joseph Evans commented on MAPREDUCE-2864:
------------------------------------------------
I went through as much of the mapreduce source as I could to find all of the
properties that are being used. There is a lot of discrepancy between them.
The plan right now is to have only a few major categories
||Category||Suggested Name||
|Application Specific Config|yarn.app.<app-name>.*|
|Map Reduce (Application Master) Config|yarn.app.mapreduce.* and mapreduce.*
for backwards compatibility reasons|
|Application ACL Config|yarn.app.acl.*|
|Yarn Specific Security Config|yarn.security.*|
|Yarn Specific IPC Config|yarn.ipc.*|
|Node Manager Config|yarn.server.nodemanager.*|
|Resource Manager Config|yarn.server.resourcemanager.*|
|MapReduce History Server|mapreduce.historyserver.*|
The mapreduce.historyserver is special because it is mapreduce specific.
Any Thoughts on this?
> Renaming of configuration property names in yarn
> ------------------------------------------------
>
> Key: MAPREDUCE-2864
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2864
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobhistoryserver, mrv2, nodemanager, resourcemanager
> Affects Versions: 0.23.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Fix For: 0.23.0
>
>
> Now that YARN has been put in to trunk we should do something similar to
> MAPREDUCE-849. We should go back and look at all of the configurations that
> have been added in and rename them as needed to be consistent and subdivided
> by component.
> # We should use all lowercase in the config names. e.g., we should use
> appsmanager instead of appsManager etc.
> # history server config names should be prefixed with mapreduce instead of
> yarn.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
