Hi Tom, Just want to let you know that back then when I tried to circumvent this problem, I used job.submit() and retrieve the counter asynchronously. I found out that the counter values always zero during the execution (so the job is still running halfway). So, in this case, the job is not retired yet, right? so, it might suggest another problem?
Felix Halim On Thu, Jul 8, 2010 at 8:13 PM, Tom White <t...@cloudera.com> wrote: > A problem was found with Job.getCounters() returning null (see > https://issues.apache.org/jira/browse/MAPREDUCE-1920). I plan to roll > a new release candidate when this is fixed. > > Cheers, > Tom > > On Fri, Jul 2, 2010 at 8:25 AM, Tom White <t...@cloudera.com> wrote: >> I have created a candidate build for Hadoop 0.21.0. This fixes over >> one thousand issues in Common, HDFS, and MapReduce since 0.20.2. >> >> This release is being classified as a minor release, which means that >> it is API compatible with 0.20.2. >> >> *** This release candidate has not been tested extensively, so it >> should not be considered stable. >> *** Please download, test and vote before the vote closes on Thursday 8 July. >> >> http://people.apache.org/~tomwhite/hadoop-0.21.0-candidate-0/ >> >> The hadoop-0.21.0.tar.gz file is an old-style combined release which >> includes Common, HDFS, and MapReduce. >> >> Thanks, >> Tom >> >> P.S. I have not yet pushed the JARs to Apache's Maven Staging >> Repository (see HADOOP-6847), but this shouldn't prevent testing and >> voting while it is sorted out. >> >
