[
https://issues.apache.org/jira/browse/MAPREDUCE-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141417#comment-15141417
]
Kuhu Shukla commented on MAPREDUCE-6603:
----------------------------------------
To have this change configurable will allow backward compatibility, such that
we can turn off the capability to report failed task counters allowing legacy
consumers of the counters to not get affected. Also, the present code has an
inconsistency where a failed task with one or more killed attempts would still
report counters versus a failed task with all failed attempts. This stems from
how TaskAttemptImpl.EMPTY_COUNTERS is used when the bestAttempt is null. This
is a static final variable that has groups attached to it which get populated,
so essentially when we assign counters to be EMPTY_COUNTERS it may have
countergroups populated through {{addGroups}} making the {{isEmpty}} call to
return false. I will update with more findings on this.
Appreciate any comments/ideas/suggestions from the community on this.
> Add counters for failed task attempts
> -------------------------------------
>
> Key: MAPREDUCE-6603
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6603
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 2.7.1, 2.6.3
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Priority: Minor
>
> The counters for failed task attempts are currently unavailable and would be
> nice to have for troubleshooting whilst not including them in the aggregate
> counters at task or job level. One should be able to view them at attempt
> level.
> {code}
> Sorry it looks like task_1_2_r_3 has no counters.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
