[
http://issues.apache.org/jira/browse/HADOOP-492?page=comments#action_12431703 ]
Owen O'Malley commented on HADOOP-492:
--------------------------------------
I would propose that the JobConf defines a list of counters that is augmented
with the "generic" ones like records, bytes, etc. The TaskTracker heart beat
then pushes a list of longs with the status of each task as part of the
heartbeats. These counters are visible as the job runs via the web/ui.
So it would look like:
job.setCounterList("foo,bar,baz");
the Reporters pick up a new field:
void addCounter(String counterName, long increment);
> Global counters
> ---------------
>
> Key: HADOOP-492
> URL: http://issues.apache.org/jira/browse/HADOOP-492
> Project: Hadoop
> Issue Type: New Feature
> Components: mapred
> Reporter: arkady borkovsky
>
> It would be nice to have map / reduce job keep aggregated counts for
> arbitrary events occuring in its tasks -- the numer of records processed, the
> numer of exceptions of a specific type, the number of sentences in passive
> voice, whatever the jobs finds useful.
> This can be implemented by tasks periodically sending <name, value> pairs to
> the jobtracker (in some implementations such messages are piggy-backed on the
> heartbeats), so that the job tracker stores all the latests values from each
> task and aggregates them on a request. It should also make the aggregated
> values available at the job end. The value for a task would be flushed when
> the task fails.
> #491 and #490 may be related to this one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
