[
https://issues.apache.org/jira/browse/MAPREDUCE-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-6958:
----------------------------------
Fix Version/s: 3.0.0-beta1
Hmm, so we have a bit of a quandry. I committed this through branch-3.0, but
when I tried picking this to branch-2 and 2.8, but the patch doesn't apply
because the mappers field was not there. I thought it had been there awhile,
but it turns out it was added in MAPREDUCE-6808 in a backwards-incompatible
way. The original format was job then reducer, and that JIRA made it job,
maps, reducer.
Since 3.0 hasn't officially shipped yet, I propose to revert the 003 patch I
committed to trunk and branch-3.0 and instead commit patch version 002 which
preserves the job-then-reducer ordering already established in the 2.x line.
Objections?
> Shuffle audit logger should log size of shuffle transfer
> --------------------------------------------------------
>
> Key: MAPREDUCE-6958
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6958
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Minor
> Fix For: 3.0.0-beta1
>
> Attachments: MAPREDUCE-6958.001.patch, MAPREDUCE-6958.002.patch,
> MAPREDUCE-6958.003.patch
>
>
> The shuffle audit logger currently logs the job ID and reducer ID but nothing
> about the size of the requested transfer. It calculates this as part of the
> HTTP response headers, so it would be trivial to log the response size. This
> would be very valuable for debugging network traffic storms from the shuffle
> handler.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
