hadoop-mapreduce-issues mailing list archives

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

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

Robert Joseph Evans commented on MAPREDUCE-2864:

Currently there are a few configs that are not intended to be set by admins or by the end
user.  They are configs that are set by the system and consumed by the system.  

For MRInternalConf this is just yarn.history.create.intermediate.base.dir which is set by
the client and is currently always set to TRUE.  It is consumed by the Application Master
when it creates the JHist file informing it to create the base directory if it does not currently

YarnInternalConfig has yarn.security.info.class.name and yarn.server.nodemanager.debug.delete.delay
in it.  The first one is set at startup by each server to indicate the class that will handle
security.  The second one is a bit different and I wasn't sure if it should be in there or
not.  It is a config that was added in to support some unit tests.  It avoids deleting temporary
files for a specific amount of time.  This way the tests can look at the files before they
are removed.

All of them I could move into *AdminConfig without any problem.  I would just put a comment
on them saying why they should not be used.

> 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


View raw message