[
https://issues.apache.org/jira/browse/WHIRR-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965572#action_12965572
]
Tom White commented on WHIRR-148:
---------------------------------
This seems not to be a problem with the JVM (the failure occurs with 1.6.0_17
and 1.6.0_21), but the AMI. The failure was seen with
amzn-ami-0.9.9-beta.x86_64-S3 (ami-827185eb) which was automatically picked by
Whirr/jclouds, but when setting {{whirr.image-id=us-east-1/ami-da0cf8b3}}
(Ubuntu 10.04 LTS Lucid) the job succeeds.
I think we should test configurations using WHIRR-92 and document them using
WHIRR-145.
> Hadoop jobs fail on large EC2 instances
> ---------------------------------------
>
> Key: WHIRR-148
> URL: https://issues.apache.org/jira/browse/WHIRR-148
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.3.0
> Reporter: Tom White
> Assignee: Tom White
>
> When using a m1.large or c1.xlarge hardware-id, jobs fail with a error like:
> {noformat}
> FAILED
> java.io.IOException: Task process exit with nonzero status of 134.
> at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:418)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
