-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
v3.3: Retrieving pod artifacts using Web UI from S3 is slow #8257
Comments
How slow is “slow”? |
I just timed pulling a 2KB log file and it took 2m 2s to appear. |
Have you tested in v3.2? |
I've got the same issue and it's only in v3.3.0 and v3.3.1. v3.2.* had no issue. |
Let me get this right+
|
yes, that's right. |
Candidates for blame:
|
Does it always take 2m2s? Are you using browser? |
I'd have to do more timings, but anecdotally they all take about the same time. |
And yes to browser. (Google Chrome) |
Looks like it. These are the logs from the wait container where the artifacts (container logs in this case) are uploaded
The main.log file is about 300KB here |
If they take the exact same time, then that hints at some problem with Argo Server in one place. |
Can you attach argo-server logs. |
During the pod run
When getting logs from UI
Maybe due to the timeouts set on my ingress, I never see the logs |
Do you have the same problem when connecting directly, rather than via ingress or LB? |
All my testing has been done when connecting through |
I think we need to do live debugging. Could you please set-up 30m? |
Zoom is not accepting my password |
I believe I'm in the waiting room now |
Hmm, I don't see your booking, maybe you got booked with someone else. Could you do 10:30am PT tomorrow? |
Yes |
Cool. Are you able to book that slot tomorrow? |
It says there are no slots available |
11am or 11:30am? |
do you see a booking for me at 1pm EST Wednesday? |
Are you still available now? |
git log --oneline v3.2.9..v3.3.0 -- go.mod f0fb0d5 chore(deps): bump github.com/minio/minio-go/v7 from 7.0.15 to 7.0.23 (#8003) |
rm |
Signed-off-by: Alex Collins <alex_collins@intuit.com>
@chriswilley I've created an engineering build that adds additional informational logging. This should help diagnose where the problem is. It will take 1h for the image to be published. The tag will be You only need to change the argo-server image tag. Leave other configration unchanged. |
Will do. Thanks. |
I think I found the cause minio-go 7.0.23 introduced a regression that is fixed in 7.0.24: minio/minio-go#1626 |
Will be fixed in v3.3.2 |
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 👍.
The text was updated successfully, but these errors were encountered: