You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/02/11 20:25:15 UTC

[jira] [Commented] (MAPREDUCE-4997) Deprecate mapreduce.jobtracker.address

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

Hitesh Shah commented on MAPREDUCE-4997:
----------------------------------------

For users to transition from MR1 to MR2, we are talking about a full cluster change - replacing the JT/TTs with new daemons - RM/NMs. In this scenario, the users would be well aware of the change and therefore have to make the necessary config changes too. Therefore, it seems like not supporting mapreduce.jobtracker.address would be more ideal so as to not give them the wrong impression that the RM is a JT replacement.
                
> 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