Re: t1.micro cluster problem

From: Adam <no email>
Date: Fri, 4 Oct 2013 14:09:24 -0400

Did you try the start command with --no-create (-x) option to see if
starcluster can reconfigure it for you? I do not recommend t1.micro
instances for anything but simple tests due to the CPU throttling.


On Fri, Oct 4, 2013 at 10:27 AM, Yehuda Landau <didist_at_gmail.com> wrote:

> Hi
> I did
> starcluster start -o -s 3 -b 0.03 -i t1.micro -n ami-765b3e1f mycluster
>
> the master initialized first but than I was pending for fulfillment of the
> other 2 spot request for a minute or two
>
> Next when I ssh into the master
> and cat the /etc/hosts (as in tutorial)
> I get:
> root_at_ip-10-194-75-77:~# cat /etc/hosts
> 127.0.0.1 localhost
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
> AND NOT
> # Do not remove the following line or programs that require network
> functionality will fail
> 127.0.0.1 localhost.localdomain localhost
> 10.252.167.143 master
> 10.252.165.173 node001
>
> Like In tutorial
>
> SO
> ssh node001 hostname
>
> DOES NOT WORK
> (no ip vs label in /etc/hosts)
>
> is it because t1.micro doesn't work well with Starcluster
> or is it a bug since I waited for the other nodes... ?
>
> Best
> Didi
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
Received on Fri Oct 04 2013 - 14:09:45 EDT