argo-workflows: v3.3: Retrieving pod artifacts using Web UI from S3 is slow
Summary
What happened/what you expected to happen?
After a pod completes, when we click on any input or output artifact (such as the main container log) in the Web UI it takes about a full minute to pull from S3. Previously on v3.1.12 it was very quick. Nothing about the network or EKS configurations have changed.
What version are you running? v3.3.0
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 5
- Comments: 34 (19 by maintainers)
Commits related to this issue
- feat: Log result of HTTP requests & artifacts load/saves. Closes #8257 Signed-off-by: Alex Collins <alex_collins@intuit.com> — committed to argoproj/argo-workflows by alexec 2 years ago
- feat: Log result of HTTP requests & artifacts load/saves. Closes #8257 (#8394) Signed-off-by: Alex Collins <alex_collins@intuit.com> — committed to argoproj/argo-workflows by alexec 2 years ago
I think I found the cause minio-go 7.0.23 introduced a regression that is fixed in 7.0.24: https://github.com/minio/minio-go/pull/1626
Will be fixed in v3.3.2
I think we need to do live debugging.
Could you please set-up 30m?
https://bit.ly/book-30m-with-argo-team