You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But when I run the batch job, it claims that there aren't any available instances of that type! And there's no "allowable instances exceeded" error, either, so I don't think it's because someone else in the org is using x1e.2xlarge.
Mon 1 Oct - 10:22 ~/code/tick-genome/pre_assembly_qc/full_workflow origin ☊ master ✔ 2☀
reflow runbatch -retry
reflow: batch program ../../reflow/pre-assembly.rf runsfile samples.csv
retrying run Undetermined_S0
retrying run tick_1_S1
retrying run tick_2_S2
reflow: run tick_2_S2: error: resources exhausted: requested resources {mem:240.0GiB cpu:8 disk:1.0GiB} not satisfiable by any available instance type
reflow: run Undetermined_S0: error: resources exhausted: requested resources {mem:240.0GiB cpu:8 disk:1.0GiB} not satisfiable by any available instance type
reflow: run tick_1_S1: error: resources exhausted: requested resources {mem:240.0GiB cpu:8 disk:1.0GiB} not satisfiable by any available instance type
EDIT: If I add x1e.4xlarge (488 GiB ram, 16 CPUs) to my list of instances, the job goes through, but I'm wondering why does it need more resources when the x1e.2xlarge instance should be sufficient?
Do you know what may be happening?
Warmest,
Olga
The text was updated successfully, but these errors were encountered:
The other question I have is, isn't Reflow supposed to launch separate instances for the separate steps of the pipeline? Why is it trying to launch the most expensive instance now to run everything in one?
Reflow generally tries to optimize for cost, so if it's cheaper to run one large instance that can fit everything, it will do that.
However, @swami-m is looking at ways to improve how instances are allocated.
Hello!
I'm running a batch job which requires a lot of memory so I added
x1e.2xlarge
(244 GiB memory, 8 CPUs) to myconfig.yml
:But when I run the batch job, it claims that there aren't any available instances of that type! And there's no "allowable instances exceeded" error, either, so I don't think it's because someone else in the org is using
x1e.2xlarge
.EDIT: If I add
x1e.4xlarge
(488 GiB ram, 16 CPUs) to my list of instances, the job goes through, but I'm wondering why does it need more resources when thex1e.2xlarge
instance should be sufficient?Do you know what may be happening?
Warmest,
Olga
The text was updated successfully, but these errors were encountered: