[
https://issues.apache.org/jira/browse/MAPREDUCE-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432104#comment-13432104
]
Jason Lowe commented on MAPREDUCE-4044:
---------------------------------------
I think this isn't as straightforward as adding a deprecation, primarily
because this is a deprecation across configuration files. yarn-default.xml and
yarn-site.xml load before mapred-default.xml and mapred-site.xml. If
yarn-site.xml sets yarn.resourcemanager.address to an appropriate value, it
will be later smashed to "local" by mapred-default.xml if we tie
yarn.resourcemanager.address to mapreduce.jobtracker.address.
In addition I think we'd need to update Configuration deprecation support to
handle multiple deprecated values mapped to the same new key (i.e.:
mapred.job.tracker *and* mapreduce.jobtracker.address would both need to map to
yarn.resourcemanager.address). I don't think the deprecation code currently
handles a many-to-one mapping, although oddly it appears to support one-to-many.
Bottom line is that this change smells pretty risky, certainly not as easy as a
one-line Configuration.addDeprecation() call. Would it make more sense from a
risk-mitigation standpoint to have Oozie set both mapred.job.tracker and
yarn.resourcemanager.address so it can work with both 1.x and 2.x?
> YarnClientProtocolProvider does not honor mapred.job.tracker property
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-4044
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4044
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.24.0, 0.23.3
> Reporter: Alejandro Abdelnur
>
> The YarnClientProtocolProvider/YARNRunner/ResourceMgrDelegate bootstrap only
> looks for 'yarn.resourcemanager.address', they ignore 'mapred.job.tracker'
> This breaks backward compatibility and creates issues in Oozie.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
