hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4997) Deprecate mapreduce.jobtracker.address
Date Mon, 11 Feb 2013 20:01:12 GMT

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

Sandy Ryza commented on MAPREDUCE-4997:


That makes sense to me.  Also, I'm going to coopt this to get rid of all the unused configs
in JTConfig so we don't start filing JIRAs for each one.

Does it make sense to add some sort of warning to let people know these configs have no effect?

> Deprecate mapreduce.jobtracker.address
> --------------------------------------
>                 Key: MAPREDUCE-4997
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4997
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
> mapreduce.jobtracker.address currently is not used, but users transitioning from mr1
to mr2 may expect their previous job configs to work, so it should be deprecated in favor
of yarn.resourcemanager.address.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message