-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Cache Clearance Causing 404 Havoc #20417
Comments
when you refer to cache, are you specifically addressing the cache layer outlined in the harbor yaml? https://github.com/goharbor/harbor/blob/main/make/harbor.yml.tmpl#L300 |
Hi harbor team, GET https://xxxxx.com/v2/xxx/library/nextcloud/manifests/latest: NOT_FOUND: artifact etscache/library/nextcloud:latest not found we will could download it just wait for a while without any other action. I guess it related with proxy cache mechanism, but I didn't find any documents about it in https://goharbor.io/docs This issue does not only occur with the Nextcloud image; it happens with any image. thank you |
Hello Harbor Team,
I've encountered a recurring issue with image caching. Specifically, after the cache is cleared, any requests to access images return a 404 error until the cache is eventually repopulated. This issue resolves itself after some time, but it does disrupt the normal flow of operations.
Steps to Reproduce:
GET https://xxxxx.com/v2/etscache/library/nextcloud/manifests/latest: NOT_FOUND: artifact etscache/library/nextcloud:latest not found
Wait about half an hour, get it again, and you can download it
Expected Behavior:
I would expect that there would be a mechanism to either prevent this issue or handle it more gracefully, rather than directly returning a 404 error to the client.
Additional Information:
I understand that this might be due to the cache rebuilding process, but any guidance on how to mitigate this issue or improve the experience would be greatly appreciated.
Thank you for your assistance and the great work you do!
Best regards,
Suning
The text was updated successfully, but these errors were encountered: