Hello guys, Wanted to understand how is job definition for batch jobs are getting created? Is it getting created while we are using

@batch

or

--with batch

?

Yes - they get created on the fly if a relevant job description doesn't already exist

Okay.. But when I am running a step with

@batch

and assigning

cpu, memory and image

It is creating a new job definition. But when I am assigning

gpu

with it. It is not creating any new job definition. And the job is getting stuck at

RUNNABLE

many fields of job definition are overridable. we only create a new job definition if you are changing a non-overridable field - image in this case.

Oh I checked the Auto-scalling groups, my account have limit on the

G spot instances

. So… The gpu instances weren’’t getting spawned.