[
https://issues.apache.org/jira/browse/MAPREDUCE-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated MAPREDUCE-1774:
------------------------------------------
Attachment: MAPREDUCE-1774.patch
Includes Sreekanth fix for the connectivity problem. It has been caused by
property names change between MR 0.20 and 0.22
- mapred.job.tracker -> mapreduce.jobtracker.address
- mapred.task.tracker.report.address ->mapreduce.tasktracker.report.address
But because MR lacks a container similar to {{DFSConfigKeys}} there's *no way*
to track such change by Java means. Except by knowing by heart ;(
Tests are running against a real 0.22 cluster now! Some issues are addressed by
HADOOP-6828 (another neat change). A couple more of issues will addressed in
the next iteration. The patch is almost ready at the moment!
> Large-scale Automated Framework
> -------------------------------
>
> Key: MAPREDUCE-1774
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1774
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Attachments: MAPREDUCE-1774.patch, MAPREDUCE-1774.patch,
> MAPREDUCE-1774.patch, MAPREDUCE-1774.patch, MAPREDUCE-1774.patch,
> MAPREDUCE-1774.patch, MAPREDUCE-1774.patch, MAPREDUCE-1774.patch,
> MAPREDUCE-1774.patch, MAPREDUCE-1774.patch
>
>
> This is MapReduce part of HADOOP-6332
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
