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 "Haibo Chen (JIRA)" <ji...@apache.org> on 2016/07/21 04:30:20 UTC
[jira] [Commented] (MAPREDUCE-6661) hostLocalAssigned remains zero
after scheduling
[ https://issues.apache.org/jira/browse/MAPREDUCE-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387134#comment-15387134 ]
Haibo Chen commented on MAPREDUCE-6661:
---------------------------------------
[~sultan] hostLocalAssigned is the # of mappers that ran on nodes where their input is also stored locally. A mapper can be scheduled to run on data-local nodes, rack-local nodes or anywhere in the cluster. The fact that hostLocalAssigned remains zero while rackLocalAssinged gets updated simply indicates that the mappers were not able to be scheduled on data-local nodes, so they were run on rack-local nodes.
> hostLocalAssigned remains zero after scheduling
> ------------------------------------------------
>
> Key: MAPREDUCE-6661
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6661
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Sultan Alamro
> Priority: Critical
>
> In the AM log file I see that the hostLocalAssigned in org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator remains zero even after scheduling, but the rackLocalAssigned gets updated (I run it in one rack)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org