-
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
GC not working properly #20431
Labels
Comments
can you execute a dry-run? You can provide the incremental log of job service pod on executing an GC. |
wy65701436
added
the
help wanted
The issues that is valid but needs help from community
label
May 20, 2024
Well after some fiddling around, I found that the GC is ongoing but there are a few issues.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We recently upgraded to Harbor 2.10 hoping that the GC would be working fine. Since there was a huge backlog of artifacts not cleaned, to circumvent this we created a new Harbor instance and replicated all the data. This helped us bring down our S3 bucket size from 200TB to 20TB.
After we moved to the v2.10.0, initially the GC was working fine for a month and was clearing around 300Gb every week but last couple of weeks the GC is erroring out and no GC logs show up in the Harbor UI.
Our harbor infra consists of the following:
EKS(with EFS storage) + RDS + S3
The text was updated successfully, but these errors were encountered: