On Tue, Jul 20, 2010 at 10:50 AM, Felix Halim <felix.ha...@gmail.com> wrote: > On Fri, Jul 16, 2010 at 6:17 PM, Tom White <t...@cloudera.com> wrote: >> Felix, I don't think this is a bug since counters are not stable until >> the job is complete, so the values you see may be zero if you retrieve >> them asynchronously. > > Just to clarify.. these counters that are retrieved asynchronously > will be updated as soon as one mapper or reducer completes, right? > Or is it going to be delayed arbitrarily until the job is finished?
To be clear, the counters objects will not be updated, you have to retrieve them again, and you can only be sure they are correct after the job completes. > > BTW, I have a warning when running a job: > > 10/07/20 17:44:19 WARN conf.Configuration: mapred.task.id is > deprecated. Instead, use mapreduce.task.attempt.id > > What causes this warning? I don't use mapred.task.id anywhere in the > configurations... I think it's used internally, so there's nothing to worry about. Tom > > Felix Halim >
