[
https://issues.apache.org/jira/browse/MAPREDUCE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732304#action_12732304
]
Jiaqi Tan commented on MAPREDUCE-479:
-------------------------------------
Traceability greatly improves the ability for diagnosis to be carried out on
the system, and I would argue that the ability for the system to be diagnosed
is a first-class feature that is important for its own sake; if the system's
operation cannot be exposed at all then that greatly detracts from the
usability of the system for users.
I would still argue for the side-effect to be maintained because needing to
perform time-based + host-based disambiguation of multiple attempts of the same
task requires the assumption that the same task will not have multiple attempts
being run on the same host, which is even more opaque than maintaining a
publicly-documented (i.e. with this JIRA) side-effect.
> Add reduce ID to shuffle clienttrace
> ------------------------------------
>
> Key: MAPREDUCE-479
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-479
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.21.0
> Reporter: Jiaqi Tan
> Assignee: Jiaqi Tan
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HADOOP-6013.patch, MAPREDUCE-479-1.patch,
> MAPREDUCE-479-2.patch, MAPREDUCE-479-3.patch, MAPREDUCE-479.patch
>
>
> Current clienttrace messages from shuffles note only the destination map ID
> but not the source reduce ID. Having both source and destination ID of each
> shuffle enables full tracing of execution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
