hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2774) Add counters to show number of key/values that have been sorted and merged in the maps and reduces
Date Tue, 25 Nov 2008 06:01:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650473#action_12650473
] 

Chris Douglas commented on HADOOP-2774:
---------------------------------------

bq. Just didn't want to change all the calls to constructors of IFile.Reader and IFile.Writer
in all files to have this extra parameter(null in most cases). So added new constructors.
After removing the old constructors, the compiler complains about 7 unmatched calls. One cstr,
{{Reader(Configuration, FileSystem, Path, CompressionCodec)}} doesn't have any callers left.
You've already done most of the work on this...

bq. Map First Level Spills: Runping wanted this for [...]
Yes, but the changes don't have to be part of this issue. It's a separate change to the counters,
and any debate about its usefulness needn't hold up the rest of the patch.

> Add counters to show number of key/values that have been sorted and merged in the maps
and reduces
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2774
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2774
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Owen O'Malley
>            Assignee: Ravi Gummadi
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-2774.patch, HADOOP-2774.patch, HADOOP-2774.patch, HADOOP-2774.patch,
HADOOP-2774.patch
>
>
> For each *pass* of the sort and merge, I would like a count of the number of records.
So for example, if the map output 100 records and they were sorted once, the counter would
be 100. If it spilled twice and was merged together, it would be 200. Clearly in a multi-level
merge, it may not be a multiple of the number of map output records. This would let the users
easily see if they have values like io.sort.mb or io.sort.factor set too low.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message