https://flyte.org
Join Slack
Hi! After bumping flyte from v1.5.0 to v1.6.0 I found that the task resource config doesn’t propagat...
# flyte-support
g
Hi! After bumping flyte from v1.5.0 to v1.6.0 I found that the task resource config doesn’t propagate to AWS Batch Job’s resource config, I define CPU and memory like this:
Copy code
@task(requests=Resources(mem="16Gi", cpu="8"), task_config=AWSBatchConfig(platformCapabilities="EC2"))
But in AWS batch it’s always 1 vcpu and 1049 mem Any idea why?
@glamorous-carpet-83516 Sorry for the ping, but do you have any idea?
g
what’s the resource limit in flyteadmin configmap
could you try limit instead?
g
I didn’t set one, I only set:
Copy code
task_resource_defaults:
    task_resources:
      defaults:
        cpu: 1000m
        memory: 1000Mi
        storage: 1000Mi
      limits:
        cpu: 256
        memory: 512Gi
        storage: 512Gi
g
how about flytekit 1.9.0
g
No luck, seems like it’s only using the default values
Do you know why or should I create an issue? @glamorous-carpet-83516
g
yes, could you create an issue, thanks
3 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by