hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2051) JobTracker's TaskCommitQueue is vulnerable to non-IOExceptions
Date Tue, 16 Oct 2007 11:12:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535223
] 

Hadoop QA commented on HADOOP-2051:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12367808/HADOOP-2051_2_20071016.patch
against trunk revision r584939.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/955/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/955/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/955/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/955/console

This message is automatically generated.

> JobTracker's TaskCommitQueue is vulnerable to non-IOExceptions
> --------------------------------------------------------------
>
>                 Key: HADOOP-2051
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2051
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.0
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: HADOOP-2051_1_20071013.patch, HADOOP-2051_2_20071016.patch
>
>
> The {{JobTracker#TaskCommitQueue#run}} method only handles {{IOException}}s. Christian
Kunz ran into a scenario where a job was stuck with all tasks in {{COMMIT_PENDING}} state
and the stack traces showed that the "Task Commit Thread" wasn't even around.
> The work-around is to model {{TaskCommitQueue#run}} along the lines of other long-running
threads in the {{JobTracer}} ({{ExpireLaunchingTasks}}, {{ExpireTrackers}} etc.) to catch,
log and ignore any {{Exception}} in a loop.

-- 
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