hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2864) Renaming of configuration property names in yarn
Date Thu, 25 Aug 2011 04:04:29 GMT

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

Mahadev konar commented on MAPREDUCE-2864:
------------------------------------------

Robert, 
 The config names look good but the config files MRInternalConf and YarnInternal conf are
a little confusing. What configs should these be storing?

> 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
>
>         Attachments: yarnConfigs.csv
>
>
> 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

        

Mime
View raw message