You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Devaraj K (JIRA)" <ji...@apache.org> on 2013/04/16 14:41:15 UTC
[jira] [Assigned] (YARN-580) Delay scheduling in capacity scheduler
is not ensuring 100% locality
[ https://issues.apache.org/jira/browse/YARN-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj K reassigned YARN-580:
------------------------------
Assignee: Devaraj K
> Delay scheduling in capacity scheduler is not ensuring 100% locality
> --------------------------------------------------------------------
>
> Key: YARN-580
> URL: https://issues.apache.org/jira/browse/YARN-580
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 2.0.2-alpha, 2.0.1-alpha
> Reporter: Nishan Shetty
> Assignee: Devaraj K
>
> Example
> --------
> Machine1: 3 blocks
> Machine2: 2 blocks
> Machine3: 1 blocks
> When we run job on this data, node locality is not ensured 100%
> Tasks run like below even if slots are available in all nodes:
> --------------
> Machine1: 4Task
> Machine2: 2Task
> Machine3: No task
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira