[
https://issues.apache.org/jira/browse/HADOOP-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614112#action_12614112
]
Chris Douglas commented on HADOOP-3748:
---------------------------------------
Sorry, you're right; disable them during the job. Are you certain that counters
are the correct tool for tracking 100-200 different quantities? You might
consider using metrics or any of a wide range of reporting frameworks, instead.
You might also consider tracking HADOOP-3719 if you've chosen Counters for
aggregation, only. You're probably right to suspect that counters are
ill-suited to this, but that counters should be configurable to scale in this
way is less obvious to me.
> Flag to make tasks to send counter information only at the end of the task
> --------------------------------------------------------------------------
>
> Key: HADOOP-3748
> URL: https://issues.apache.org/jira/browse/HADOOP-3748
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Environment: all
> Reporter: Alejandro Abdelnur
>
> Currently counters are streaming from the task to the jobtracker as the task
> progresses. If the number of counters is large this has a significant impact
> on the network traffic as well as in the JobTracker load.
> The should be a flag, for example by counter-group, that indicates that the
> counters are to be reported at the end of the task. By default this flag
> should be set to false for all counter-groups maintaining the current
> behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
