Skip to content
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

Scaling Garbage Collector #17836

Closed
honzasara opened this issue Nov 22, 2022 · 2 comments
Closed

Scaling Garbage Collector #17836

honzasara opened this issue Nov 22, 2022 · 2 comments
Assignees
Labels
area/gc kind/requirement New feature or idea on top of harbor

Comments

@honzasara
Copy link

My Harbor use Swift Storage, we have not any problem with this.

but, we have about 10TB in this storage. Garbage Collector is too lazy. One run spent about 7 days.

It is possible to run the Garbage Collector in multiple instances ?

H.

@Vad1mo Vad1mo added kind/bug kind/requirement New feature or idea on top of harbor labels Nov 22, 2022
@chlins chlins added the area/gc label Nov 28, 2022
@chlins chlins removed the kind/bug label Nov 28, 2022
@honzasara
Copy link
Author

Hello,

i have details on this the problem. The problem is not big storage. But the problem is number of images. More image is new created/uploaded and more images is removed.

H.

@wy65701436
Copy link
Contributor

As harbor has introduced the parallel deletion since v2.9.0, you can set the workers to 5 and see if it's satisfy your request. Reopen it if it is still a blocker in your side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gc kind/requirement New feature or idea on top of harbor
Projects
None yet
Development

No branches or pull requests

4 participants