-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question on restarting ec-2 cluster #11
Comments
What instance types are you using? Are they EBS-backed? If you happen to still have the log available, you might try pasting the relevant bits here so that I can better-diagnose. Also -- I have several restart-related bugfixes that I'm expecting to push out today, and I suspect that one of them might be impacting you. |
Ah okay that is most likely what I missed, so how would I go about disabling the EBS-backend? I was reading through the starcluster - http://star.mit.edu/cluster/docs/0.92rc2/manual/configuration.html docs and it seems like you would enable EBS volumes through a [volume] section, is that right? I don't see the volume mentioned anywhere in the myriacluster.config. In the myriaplugin.py, there is a path parameter that is set to On the other hand, if I did disable the EBS-backend, then I'd be left with less storage, is that true? Or am I completely misunderstanding the point of the EBS volumes? Below is the error that I got because I tried to restart a machine with an EBS-backend:
Thanks again! I'll check out the new bugfixes once they are out. This isn't super urgent for me, but I just wanted to check it out to test and know what I could do with this feature. |
"EBS-backed" just refers to the boot volume, not to any other EBS volumes On Thu, Apr 2, 2015 at 3:29 PM, jortiz16 notifications@github.com wrote:
|
And I was using 5 m1.large on-demand instances |
Thanks @senderista ! That makes sense, I was only thinking of the EBS volumes directly attached to the instances |
This is super weird. The Myria deployment script should be automatically creating |
So I shut down that cluster earlier, but I saved my config file. I can retrace my steps and retry this to check whether |
I was trying out the ability to start/restart myria-ec2 instances. Last night I started a cluster of 5 on-demand instances and stopped them. This morning, I tried to start them up again by running "starcluster start -x mycluster". My cluster did turn on, but there was an error when it tried to start up myria.
From the logs, it seems like starcluster was trying to issue an rsync command to /mnt/myria_ec2_deployment , which does not exist. So I was thinking I am probably not setting up or restarting correctly?
The text was updated successfully, but these errors were encountered: