hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5337) JobTracker greedily schedules tasks without running tasks to join
Date Thu, 19 Mar 2009 09:07:51 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amar Kamat updated HADOOP-5337:
-------------------------------

    Attachment: HADOOP-5337-v1.7.patch

Attaching a patch the delays the scheduling while all the expected trackers are discovered.
Result of test-patch
{code}
[exec] +1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 6 new or modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec] 
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
     [exec] 
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.
{code}

Attaching a simple testcase.

> 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
>         Attachments: HADOOP-5337-v1.7.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.


Mime
View raw message