Hi, I am getting the following error when running a workflow:

failed at Node[n2]. BindingResolutionError: Error binding Var [wf].[cv_res], caused by: failed at Node[n1]. CausedByError: Failed to GetPrevious data from outputDir [<s3://flyte-metadata/metadata/propeller/model-fdd918cd6b2c34e3ea92/n3/data/0/n1/0/outputs.pb>], caused by: path:<s3://flyte-metadata/metadata/propeller/model-fdd918cd6b2c34e3ea92/n3/data/0/n1/0/outputs.pb>: [LIMIT_EXCEEDED] limit exceeded. 3mb > 2mb.

I found this github discussion about changing the storage limit. We are using the

flyte-binary

chart. Should I add the

maxDownloadMBs

under

configuration.storage

?

configuration:
  storage:
    metadataContainer: "${metadata_bucket}"
    userDataContainer: "${userdata_bucket}"
    provider: s3
    providerConfig:
      s3:
        region: "${region}"
        authType: "iam"

Thanks!

yes

@Ketan (kumare3) I tried it like this and it didn't work, still getting the same error.

storage:
    metadataContainer: "${metadata_bucket}"
    userDataContainer: "${userdata_bucket}"
    provider: s3
    providerConfig:
      s3:
        region: "${region}"
        authType: "iam"
    limits:
      maxDownloadMBs: 6

That is how it is shown in the github discussion. Does that need to go somewhere else for

flyte-binary

values.yaml?

looks like that's the right way to configure `maxDownloadMBs`: https://github.com/flyteorg/flyte/blob/dfb56f4639a57d519d8fc48cae7d192a385fc160/deployment/sandbox/flyte_helm_generated.yaml#L696.

@Nandakumar Raghu I think your indentation looks wrong

@Ketan (kumare3) looks alright to me..

interesting

We don’t have have two storage sections, I just put together the storage section from the example @Samhita Alla shared and what we are using to check the indentation.

@Dan Rammer (hamersaw) could you help us figure out why this isn't working?

Hey @Samhita Alla Dan is out for a few days