[
https://issues.apache.org/jira/browse/MAPREDUCE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089785#comment-13089785
]
Robert Joseph Evans commented on MAPREDUCE-2864:
------------------------------------------------
I have also been looking at the files that these configurations are stored in
and I would like to propose an new layout to the files.
||Class||Description||
|YarnUserConf|This will store keys and defaults for configs that a user of yarn
(like mapreduce) may want to set|
|YarnAdminConf|This will store keys and defaults for configs that a yarn
cluster admin may want to set|
|YarnInternalConf|This will store keys and defaults for configs that yarn uses
internally, If any, and should not be set by someone else|
|MRUserConf|This will store mapreduce specific keys and defaults that an
mapreduce user may want to set. For backwards compatibility many of these
types configs will not move from where they are now, but this is likely to
reference them.|
|MRInternalConf|This will store mapreduce specific keys and defaults that mr
uses internally|
Some configs that are specific to something that is pluggable, and may be
completely replaced (like the scheduler) will remain where they are now.
The user and admin would be placed in the API jars and the internal would
probably be placed under the common or core jar.
Any comments 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
