Batch - Newly created job isn't starting? Stuck in Queued status?

For some reason this morning several Batch jobs which I’ve attempted to create are getting stuck and not getting past the “Queued” state. As a result no Compute Engine VM ever gets created and nothing happens.

All this was working fine yesterday.

Is this an issue on Google’s backend?

There doesn’t seem to be a widespread issue with the backend. Can you share more details on your job and the details from the describe command

gcloud batch jobs describe  --location 

When I create a n1**-highmem-16** machine and while utilizing 104Gb and all 16 vCPU’s I have no issues.

However when I create a n1-highmem-32 machine it just hangs and it will not create the Batch job.

When I look into the job itself I notice the Machine type will just display No value as you can see in the screenshot.

I had the same behavior today when attempting to create a vm utilizing a C2 series machine.

Okay, wow.

I ran the command you mentioned @Shamel and I see this message:

"type: SCHEDULING_INFO

  • description: 'Quota checking process decides to delay scheduling for the job jobname-blah-xadas
    due to inadequate quotas [Quota: CPUS, limit: 24, usage: 0, wanted: 32.]"

The fact that I wanted to use 32 vCPU’s means I’m bypassing some quota? :downcast_face_with_sweat:

How do I raise this?

The page below has details on working with quotas and quota increase requests.

https://cloud.google.com/docs/quota

1 Like

Thank you for all the help, this worked!