whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-490) hadoop-mapreduce.mapred.child.ulimit should be unlimited by default
Date Wed, 01 Feb 2012 21:40:58 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198179#comment-13198179

Andrei Savu commented on WHIRR-490:

Jai this was the only change you've made to make things work? 
> hadoop-mapreduce.mapred.child.ulimit should be unlimited by default
> -------------------------------------------------------------------
>                 Key: WHIRR-490
>                 URL: https://issues.apache.org/jira/browse/WHIRR-490
>             Project: Whirr
>          Issue Type: Bug
>          Components: service/hadoop
>    Affects Versions: 0.7.0
>         Environment: Hadoop Cluster on Amaazon EC2
>            Reporter: Jai Kumar Singh
>            Assignee: Andrei Savu
>             Fix For: 0.7.1
>         Attachments: WHIRR-490.patch
> Last week, I was struggling to run hadoop job(simple wordcount example program comes
with hadoop ) on amazon ec2. Jobs were dying saying
> " Could not create the Java virtual machine ". It took me a while to figure out that
ulimit was the problem. Whirr by default assign ulimit to a constant number but not unlimited.
Setting mapred.child.java.opts to any number ( I tried from 64mb to 4096mb on t1.micro instances
to m2.4xlarge ) was throwing error.
> More details on 
> https://issues.apache.org/jira/browse/HADOOP-7989

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message