https://prefect.io
Join Slack
Hi :wave: A quick one. When using the new ECS push work pool, how would define custom CPU and memory...
# ask-community
y
Hi đź‘‹ A quick one. When using the new ECS push work pool, how would define custom CPU and memory size for a task?
âś… 1
We’ve tried:
Copy code
- name: migrate_users_to_no_steps_buckets
  entrypoint: jobs/migrate_users_to_no_steps_buckets/migrate_users_to_no_steps_buckets.py:migrate_users_to_no_steps_buckets
  work_pool:
    name: main
  job_variables:
    cpu: 4096
    memory: 8192
But it won’t register:
Any idea what is the correct syntax?
b
Copy code
- name: default
    version: '{{ commit-hash.stdout }}'
    tags:
      - my-tag
    schedule:
      cron: 0 3 * * *
      timezone: UTC
    entrypoint: dir/to_flow.py:myflow
    work_pool:
      <<: *es_ecs_work_pool
      job_variables:
        <<: *ecs_work_pool_overrides
        family: this__default
        cpu: 2048
        memory: 16384
y
@Ben Muller Is the “<<: *ecs_work_pool_overrides” mandatory?
k
in the sample you posted, is the indentation there exactly how it looks in your 
prefect.yaml
? 
job_variables
should be part of the 
work_pool
like so:
Copy code
work_pool:
    name: main
    job_variables:
      cpu: 4096
      memory: 8192
đź‘€ 1
🙌 1
b
@Yaron Levi no, that's just a variable override I'm yaml if you want to type stuff less
🙌 1
y
@Ben Muller @Kevin Grismore Thanks! works now.
🙌 2
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by