How to accelerate Harbor garbage collection (GC) #22734
Unanswered
microyahoo
asked this question in
Q&A
Replies: 1 comment
-
|
What storage type are you using? Please try the latest version of Harbor, as we’ve increased the worker count to 10. |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
In the current production environment, the rate of image creation far exceeds the speed of GC, leading to a continuous increase in the storage space occupied by the image registry. Taking the deletion of
simulation-jobs/single-frame sha256:1a4b70b3af7b490abe4edc67b3292fb5698b10f94b552a0681cde5d95fed599bas an example, deleting a single manifest takes 34 minutes. Currently, GC is performed by only 5 workers, resulting in extremely low efficiency.https://github.com/goharbor/harbor/blob/v2.11.0/src/jobservice/job/impl/gc/garbage_collection.go#L336-L370
https://github.com/goharbor/harbor/blob/v2.11.0/src/jobservice/job/impl/gc/util.go#L41C1-L53C2
https://github.com/goharbor/harbor/blob/v2.11.0/src/pkg/registry/client.go#L333-L357
gc.log
Beta Was this translation helpful? Give feedback.
All reactions