[
https://issues.apache.org/jira/browse/WHIRR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913082#action_12913082
]
Zach Bailey edited comment on WHIRR-96 at 9/21/10 1:07 PM:
-----------------------------------------------------------
Another problem I ran into initially was the volumes created using the
"create-storage" command were neither partitioned nor formatted with a
filesystem. I verified this by logging on to the nodes individually and running:
$ ls -la /dev/sd*
which returned only the raw devices (/dev/sdj and /dev/sdk). Had those volumes
been partitioned I would have at least seen two more entries (/dev/sdj1 and
/dev/sdk1). And, obviously, without having any partition on the volume there's
no possibility of them having a filesystem.
I thought this was the root cause of the problem that was keeping the
jobtracker from starting but ultimately even after fixing this problem the
volumes still fail to mount cleanly.
I followed the instructions here:
http://help.rightscale.com/cgi-bin/rightscale.cfg/php/enduser/std_adp.php?p_faqid=12&p_created=1221775401
for partitioning and formatting my EBS volumes on each node. The only thing I
did differently was using the ext3 filesystem instead of ext2.
was (Author: znbailey):
Another problem I ran into initially was the volumes created using the
"create-storage" command were neither partitioned nor formatted with a
filesystem. I verified this by logging on to the nodes individually and running:
$ ls -la /dev/sd*
which returned only the raw devices (/dev/sdj and /dev/sdk). Had those volumes
been partitioned I would have at least seen two more entries (/dev/sdj1 and
/dev/sdk1).
I thought this was the root cause of the problem that was keeping the
jobtracker from starting but ultimately even after fixing this problem the
volumes still fail to mount cleanly.
> EBS cluster doesn't work with CDH3 on Lucid
> -------------------------------------------
>
> Key: WHIRR-96
> URL: https://issues.apache.org/jira/browse/WHIRR-96
> Project: Whirr
> Issue Type: Bug
> Components: contrib/python
> Reporter: Tom White
>
> Following the instructions with
> https://docs.cloudera.com/display/DOC/Using+Persistent+Clusters and
> ami-2d4aa444 gives "Timeout while waiting for Hadoop to start. Please check
> logs on cluster."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
