Replies: 1 comment
-
No reason. We would gladly take a PR to change these values if you'd like to contribute it 🙏 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
MinIO Go has a built-in retry mechanism with the following default behavior:
This results in the following backoff ranges:
The MinIO Go SDK exposes these as package-level variables that can be customized:
minio.DefaultRetryUnitminio.DefaultRetryCapminio.MaxRetrySee:
https://pkg.go.dev/github.com/minio/minio-go/v7#pkg-variables
I looked through Tempo’s S3 config (specifically tempodb/backend/s3/config.go) and couldn’t find a way to configure these retry settings.
Is there a reason these are not exposed today? Would it be acceptable to add options to control the retry behavior?
This would be useful for environments where the default retry behavior is too aggressive.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions