This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Thanks for the information @echap! The quota check is purely a read on
quota status of the project and won't hold quotas. I am not sure if this
could happen due to zonal stock out, let me ask around and get back to
you, thanks!
Hi echap@, It is true that when the job can't allocate the GPU, it
returns to the queued state. But the quota check will query the current
quota usage of the project instead of actually consuming the quota.
Especially "after deleting the batch job, t...
Hi echap@, 1. May I know the Batch job uids and their regions that
encountered the above issues, so we can investigate in them? 2. Also,
you can try to describe job. There usually will be important events
logged in the job status events. If you could...
Hi @schmat_90 , I tried a job with two buckets and docker containers. It
worked for me, here is my job configuration: { "task_groups":[ {
"task_spec":{ "runnables": [ { "container": { "imageUri": "bash",
"commands": [ "-c", "sleep 1000" ] } } ], "vol...
Hi @xarauzo, could you please share more about the volume configuration
in your job? Just a head up, for existing pd, only ro is supported:
https://cloud.google.com/batch/docs/create-run-job-storage#use-persistent-disk.
Thanks! Wen