Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Housekeeping] Use single configuration option for maximum blobstore size #4487

Open
2 tasks done
hamersaw opened this issue Nov 27, 2023 · 1 comment
Open
2 tasks done
Assignees
Labels
backlogged For internal use. Reserved for contributor team workflow. exo housekeeping Issues that help maintain flyte and keep it tech-debt free

Comments

@hamersaw
Copy link
Contributor

Describe the issue

Currently there are multiple configuration values for the maximum size for a blobstore file between I/O writing, dynamic closure offloading, etc.

What if we do not do this?

Users frequently run into issues with increasing the maximum size with unclear instructions on what values need to change.

Related component(s)

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@hamersaw hamersaw added housekeeping Issues that help maintain flyte and keep it tech-debt free exo backlogged For internal use. Reserved for contributor team workflow. labels Nov 27, 2023
Copy link

dosubot bot commented Nov 27, 2023

🤖

It seems like you've got this under control, if you want help or have specific questions, let me know what I can do for you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlogged For internal use. Reserved for contributor team workflow. exo housekeeping Issues that help maintain flyte and keep it tech-debt free
Projects
None yet
Development

No branches or pull requests

2 participants