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 "Mahadev konar (Updated) (JIRA)" <ji...@apache.org> on 2012/02/02 19:38:54 UTC
[jira] [Updated] (MAPREDUCE-3697) Hadoop Counters API limits
Oozie's working across different hadoop versions
[ https://issues.apache.org/jira/browse/MAPREDUCE-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated MAPREDUCE-3697:
-------------------------------------
Attachment: MAPREDUCE-3697.patch
This is preliminary patch. This actually works but changes the iterator api on Counters to be parametarized for groups with a Counters.Counter.
I was able to run Oozie 3.1.0 (compiled against 0.20.205) jobs on a 0.23 cluster with this patch. Am trying to make the changes minimal so that the iterator is backwards compatible as well.
> Hadoop Counters API limits Oozie's working across different hadoop versions
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-3697
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3697
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: John George
> Assignee: Mahadev konar
> Priority: Blocker
> Attachments: MAPREDUCE-3697.patch
>
>
> Oozie uses Hadoop Counters API, by invoking Counters.getGroup(). However, in
> hadoop 23, org.apache.hadoop.mapred.Counters does not implement getGroup(). Its
> parent class AbstractCounters implements it. This is different from hadoop20X.
> As a result, Oozie compiled with either hadoop version does not work with the
> other version.
> A specific scenario, Oozie compiled with .23 and run against 205, does not
> update job status owing to a Counters API exception.
> Will explicit re-compilation against the relevant hadoop jars be required each
> time? This will prevent launching a uniform Oozie version across different
> clusters.
--
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