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 "Liyin Liang (JIRA)" <ji...@apache.org> on 2011/01/23 11:24:44 UTC
[jira] Updated: (MAPREDUCE-2271) TestSetupTaskScheduling failing in
trunk
[ https://issues.apache.org/jira/browse/MAPREDUCE-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liyin Liang updated MAPREDUCE-2271:
-----------------------------------
Attachment: 2271-1.diff
With [MAPREDUCE-2207|https://issues.apache.org/jira/browse/MAPREDUCE-2207], a tracker can't get any task-cleanup-task, if it has tasks with _FAILED_UNCLEAN_ state. The _testNumSlotsUsedForTaskCleanup_ of _TestSetupTaskScheduling_ creates a dummy tracker status with two _FAILED_UNCLEAN_ tasks to report. So the jobtracker return null when call _getSetupAndCleanupTasks_ with this tracker status.
I think it's useless to add task status to the tracker status in that test case, because the job already has two task-setup-tasks to schedule and the job's two tasks's status are _FAILED_UNCLEAN_. In other words, the job's tasks status need not to be updated.
So we can just remove _addNewTaskStatus_ codes as 2271-1.diff.
> 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
> 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.