hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Daley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3104) MultithreadMapRunner keeps consuming records even if trheads are not available
Date Fri, 28 Mar 2008 19:46:28 GMT

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

Nigel Daley commented on HADOOP-3104:
-------------------------------------

Hudson is down right now.  The machine is getting new memory. 

In the interest of time, I ran the test-patch target on this.  Here's the output:

      -1 overall.
     
          @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).
     
          findbugs +1.  The patch does not introduce any new Findbugs warnings.

The javac issue is that a new private class does not have a serialVersionUID which is acceptable.

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


Mime
View raw message