gorgeous-beach-23305
10/24/2023, 4:41 PMfailed 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!freezing-airport-6809
freezing-airport-6809
gorgeous-beach-23305
10/25/2023, 12:19 PMstorage:
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?gorgeous-beach-23305
10/30/2023, 10:45 AMtall-lock-23197
freezing-airport-6809
gorgeous-beach-23305
11/16/2023, 8:45 AMfreezing-airport-6809
freezing-airport-6809
freezing-airport-6809
gorgeous-beach-23305
11/16/2023, 9:01 PMtall-lock-23197
freezing-airport-6809
freezing-airport-6809