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-3104) MultithreadMapRunner keeps consuming records even if trheads are not available
Date Fri, 28 Mar 2008 22:14:24 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583212#action_12583212

Hadoop QA commented on HADOOP-3104:

-1 overall.  Here are the results of testing the latest attachment 
against trunk revision 619744.

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

    tests included +1.  The patch appears to include 3 new or modified tests.

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

    javac -1.  The applied patch generated 568 javac compiler warnings (more than the trunk's
current 567 warnings).

    release audit +1.  The applied patch does not generate any new release audit warnings.

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

    core tests -1.  The patch failed core unit tests.

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

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

This message is automatically generated.

> MultithreadMapRunner keeps consuming records even if trheads are not available
> ------------------------------------------------------------------------------
>                 Key: HADOOP-3104
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3104
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.16.1
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>            Priority: Critical
>             Fix For: 0.16.2
>         Attachments: patch3104-2.txt, patch3104-3.txt, patch3104.txt, patch3104.txt
> The ExecutorService execute() method does not block when there are not threads available,
it queues up the runnables until there are threads. 
> The problem is that all key/values are read and kept in memory for the task, with large
datasets this will create a OOM exception.
> Have to figure out how to use the execute in blocking fashion.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message