You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2009/03/24 19:52:50 UTC

[jira] Commented: (HADOOP-5564) hadoop command uses large JVM heap size

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

Suresh Srinivas commented on HADOOP-5564:
-----------------------------------------

I have tested this manually by making sure {{hadoop}} command takes the patch of changed code and it prints the {{JAVA_PLATFORM}} successfully.

> hadoop command uses large JVM heap size
> ---------------------------------------
>
>                 Key: HADOOP-5564
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5564
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: build
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: 5564.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.