You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Harsh J (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/31 10:46:31 UTC

[jira] [Resolved] (MAPREDUCE-66) The local bytes read of Mapper tasks are too high than bytes written

     [ https://issues.apache.org/jira/browse/MAPREDUCE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J resolved MAPREDUCE-66.
------------------------------

    Resolution: Not A Problem

This can be explained by looking at the task logs and the sort outputs.
                
> The local bytes read of Mapper tasks are too high than bytes written
> --------------------------------------------------------------------
>
>                 Key: MAPREDUCE-66
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-66
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Runping Qi
>
> The local bytes read are 6 times that of local bytes written.
> This is very hard to explain.
> Here is the relevant counters:
> Counters for tip_200810170704_0044_m_000001
> File Systems
> 	Local bytes read 	6,684,486,486
> 	Local bytes written 	1,007,113,506
> 	HDFS bytes read 	147,200,700
> Map-Reduce Framework
> 	Map input records 	3,588,883
> 	Map output records 	3,588,883
> 	Map input bytes 	147,200,579
> 	Map output bytes 	464,822,403
> 	Combine input records 	0
> 	Combine output records 	0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira