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 "Amar Kamat (JIRA)" <ji...@apache.org> on 2009/04/01 05:46:50 UTC
[jira] Commented: (HADOOP-5337) JobTracker greedily schedules tasks
without running tasks to join
[ https://issues.apache.org/jira/browse/HADOOP-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694368#action_12694368 ]
Amar Kamat commented on HADOOP-5337:
------------------------------------
{{TestBackupNode}}, {{TestDatanodeBlockScanner}} passed on my box. {{TestCapacityScheduler}} fails on trunk.
> JobTracker greedily schedules tasks without running tasks to join
> -----------------------------------------------------------------
>
> Key: HADOOP-5337
> URL: https://issues.apache.org/jira/browse/HADOOP-5337
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Karam Singh
> Assignee: Amar Kamat
> Attachments: HADOOP-5337-v1.11.patch, HADOOP-5337-v1.12.patch, HADOOP-5337-v1.7.patch, HADOOP-5337-v1.9.patch
>
>
> This issue was observed when JobTracker was restarted 3 times and observed that 4 instances of each reduce task were running. This issue is observed when cluster is not fully occupied.
> In testcase: Map/reduces capacity is 200/200 slots respectively and Job profile is 11000 maps, 10 reduces and speculative execution is off. JobTracker was restarted 3 times in small intervals of about 5 mins and after recovery, 40 reduce tasks were running. Task details web page (taskdetails.jsp) was showing 4 running attempts of each reduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.