Platform: GCP ✅


(Nikhil Utane) #438

I have just started using this by @arunoda. With this you can change the instance type and zone on the fly so with this you should never be locked out from accessing your code as you can always spawn a non-GPU instance.

Also, did you try without preemptible option? This should be same as using dedicated instance as opposed to spot in AWS.


(Ritesh Chaurasia) #439

Thanks


(Nikhil Utane) #440

Hi Paul,

Today I got the same problem. No resources for my instance in us-west2-b zone. So this is what I did to make my instance setting dynamic as per this blog post.

You can follow these steps if you already have an instance created as per the official procedure (instance with a specific GPU attached to it).

  1. Go to VM Instances. Edit and deselect the option ‘Delete boot disk when instance is deleted’.
  2. You can now delete your VM instance. This will not delete the disk.
  3. Follow the blog and create the (a) network, (b) firewall-rules
  4. You can then use the gcloud beta compute command to create an instance with the required choice of GPU (or without it) and attach to the disk. That way you can ALWAYS get access to the code.
  5. Though it is possible to move instances between zones, I have created a new project in different location and will use whichever has GPU resource available.

Let me know if this helps your case.

EDIT: I ran into environment related issues. When i tried again the fastai-shell commands worked (earlier they didn’t). This is better option as it allows you to move the instance to any zone where GPU is available.


(SJH) #441

thanks for helping. The issue ended up being that I somehow (accidentally) blocked port 22 so I was effectively unable to ssh in. Created a new instance all is well.


(Ramanan Thiyagarajan) #442

I’ve edited my VM instance to remove the GPU and then I can start it without any resource issue.
This could be an option if you can work on CPU or just want to get your data off GCP (like me).


(Jason) #443

How do we run tmux because the jupyter server is already running when I start the instance?


(Gaurav Desai) #445

Finally I was able to launch an instance using your utility. Thanks a lot for your help and also for making such a nice utility tool.


(Gaurav Desai) #446

@czechcheck Received my GCP credits. Thanks a lot to you for helping out fellow learners.


(noskill) #447

Reptyr is the tool. :slight_smile: . Although your notebooks won’t stop even if you ssh out of the session. The jupyter runs in background. I had mentioned that they stop in previous replies. Apologies for that


(Jason) #448

I lost my internet connection at one point and when it was back up I could not reconnect to jupyter without ssh’ing in again and starting all over by executing my notebook cells to where I was up to. When running tmux it protects you from that and any running processes on the server would still be running - so my jupyter notebooks would still work in the browser.
Reading up on Reptyr now to see how it works and can help


#449

I’m a little confused here.
In my experience when you drop the session the jupyter server should still be running and your notebook along with it.
The only issue I have been having is that you lose any output of currently running cells.
Am I wrong in thinking those cells are still running? I’ve never waited them out, i’m too impatient.


(Jason) #450

When I spin up my instance again I will explicitly test this out… When it happened to me yesterday I simply could not get the notebook to connect again without running the gcloud ssh command again. Is it because when I do ssh I’m mapping the ports to locahost… thats probbaly why. :wink:


(George Zhang) #451

It happens. You did nothing wrong. It just happens some time. GCP probably has a more limited number of GPUs (need verification) compared to AWS. So when too many people start their instances, they run out of GPUs.

I would recommend having multiple instances set up in different zones. A simple way to go would be creating a snapshot of the disk of your current instance, then create same kinds of instances using that in different zones. When the resource is in demand, simply try all of them.

GCP is great in terms of UX and pricing, but in some sense it under-prices its instances and, as a result, they are too popular and sold out. That is the price we have to pay for it.


(Arunoda Susiripala) #452

That’s a good one.
But I think what has happened last weekend is some issue they had internally.
We couldn’t start normal instances as well.


(George Zhang) #453

Did you find an official explanation about the service outage? Love to know.


(Shashank Gupta) #454

Thanks for your great help, I got credit of 500$ from your referral :slight_smile:


(Arunoda Susiripala) #455

I’m not sure about an official update.
But there was a thread on HN about this.
See: https://news.ycombinator.com/item?id=18428497


(John Hartquist) #456

I’m also having this issue. When the API is not configured correctly, there is a different error: “401 - Not Authorized”, however on GCP compute engine instances, the kaggle commandline does not seem to work. I got it working on my personal box, but not in the cloud.


(Arunoda Susiripala) #457

I had the same issue.
Then I created a new instance (with a new IP), things works again.

I think kaggle is doing some IP level blocking.


(Sander de Ruiter) #458

Does anyone suddenly have issues with not being to access any notebook? It worked 10 hours ago on my GCP instance, but right now I’m getting 403 Forbidden errors on all my notebooks. Have tried different browsers, but nothing works.

Any hints?