[
https://issues.apache.org/jira/browse/MAPREDUCE-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987020#action_12987020
]
Liyin Liang commented on MAPREDUCE-2271:
----------------------------------------
Hi Todd,
I think the test case testNumSlotsUsedForTaskCleanup is supposed to check
that one task-cleanup task only need one slot even for high RAM jobs. This test
case create a fake high RAM job with one map task and one reduce task. Each
task require 2 slots. Then check that each heartbeat will schedule one
task-cleanup task which need only one slot. So it need't to create dummy
tracker status with FAILED_UNCLEAN tasks.
The result of the change in MAPREDUCE-2207 is that task-cleanup tasks can't
be scheduled to trackers with FAILED_UNCLEAN tasks to report during heartbeat,
no matter the task failed on which tracker. This cause none task-cleanup task
will be scheduled during heartbeat in the test case. The following code:
{code:}
List<Task> tasks = jobTracker.getSetupAndCleanupTasks(ttStatus);
{code}
will always return *null*, only if ttStatus has tasks with FAILED_UNCLEAN
status.
> TestSetupTaskScheduling failing in trunk
> ----------------------------------------
>
> Key: MAPREDUCE-2271
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2271
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Liyin Liang
> Priority: Blocker
> Attachments: 2271-1.diff
>
>
> This test case is failing in trunk after the commit of MAPREDUCE-2207
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
