future-hospital-70237
06/03/2025, 6:25 AMRemote output size exceeds max
jolly-florist-66728
06/03/2025, 6:25 AMRemote output size exceeds max
means that a Flyte task tried to write an output file (such as outputs.pb) that is larger than the maximum allowed size configured for remote outputs. When this happens, FlytePropeller fails the task with an OutputSizeExceeded
error, and the workflow may get stuck or fail if the error is not properly propagated. The default max output size is often set to 10MB, but this can be configured in FlytePropeller settings. See example and discussion in Flyte Issue #381 and the relevant handler code.
Would you like more detail on how to resolve or configure this limit?
Sources:
- Flyte Issue #381
- handler.go (FlytePropeller) π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.future-hospital-70237
06/03/2025, 6:26 AMjolly-florist-66728
06/03/2025, 6:26 AMViewing logsβΎ
future-hospital-70237
06/03/2025, 6:29 AMjolly-florist-66728
06/03/2025, 6:29 AMstorage.limits.maxDownloadMBs
parameter in your Flyte deployment configuration. For example, in a Helm values file, you can add:
configuration:
inline:
storage:
limits:
maxDownloadMBs: 100
This sets the maximum allowed output size to 100MB. See Flyte Issue #4951 for details.
Would you like more detail on where to place this configuration or how it interacts with other settings?
Sources:
- Flyte Issue #4951 π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.future-hospital-70237
06/03/2025, 6:31 AMjolly-florist-66728
06/03/2025, 6:31 AM