Serverless Instance stuck initializing
Hey I'm trying to spin up a serverless instance, I've had it working fine, but as soon as I try to attach a volume that I'm using as a cache, it is stuck initializing indefinitely.
I have workers available, and nothing else has changed. Has anyone else had this issue?
Solution:Jump to solution
got it working EU-RO-1 seems most suitable, and my instance is now initializing as expected. Thanks for the help @nerdylive legend!
19 Replies
whats the logs like can you take a screenshot or copy paste
is there any capacity at the moment for the gpu ?
no usage, nothing. 16GB GPU
ahhhh
hmmm?
oh its unavailable
is is because it's unavailable suddenly?
right so that probably means my volume doesn't work with it
because maybe when you're not using network volume you're using global availability
but when you're using network volume, you're stuck with one region
I wonder what the ideal region is with the volume for max avilability
Try to pick another region and check or use the current gpu's
this is pretty limiting
Yep, i heard runpod's team gonna work on this
Is there any info on what regions the serverless instance GPUS are onm?
tooltip shows it
yeah supposed to be there
i guess this works
Solution
got it working EU-RO-1 seems most suitable, and my instance is now initializing as expected. Thanks for the help @nerdylive legend!
np