hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5564) hadoop command uses large JVM heap size
Date Fri, 28 Aug 2009 16:13:57 GMT

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

Edward Capriolo commented on HADOOP-5564:
-----------------------------------------

Steve,

You definitely need this patch with java update 14&15. I have 18.3 and u 15. There are
no surface errors! but my map tasks produced no output! Good thing I caught it relatively
quickly. 




> hadoop command uses large JVM heap size
> ---------------------------------------
>
>                 Key: HADOOP-5564
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5564
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: 5564.patch, 5564.trunk.patch, 5564.trunk.patch
>
>
> Command used to determine JAVA_PLATFORM in bin/hadoop command does not set the heap size.
The command uses default 1GB heap size. The tasks invoking hadoop command end up  using large
heap size in streaming jobs. If the maximum memory that can be used by a task is restricted,
this could result in map/reduce job failures.

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