You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Runping Qi (JIRA)" <ji...@apache.org> on 2007/10/09 15:38:50 UTC

[jira] Issue Comment Edited: (HADOOP-2010) the counter for map input locality should be associated with a map attempt

    [ https://issues.apache.org/jira/browse/HADOOP-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533209 ] 

runping edited comment on HADOOP-2010 at 10/9/07 6:38 AM:
-------------------------------------------------------------

The per mapper attempt locality attribute should have three possible values: host_local, rack_local (for future extension), and remote.



      was (Author: runping):
    
The per mapper attempt locality attribute should have three possible values: 0 for host_local, 1 for remote, 2 for rack_local (for future extension).


  
> the counter for map input locality should be associated with a map attempt
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-2010
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2010
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.16.0
>
>
> Instead of being a job counter for map locality that is on the job, each map attempt should be 0 or 1 for whether it was data-local or not.

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