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

CPU and Memory full on Harbor database server #21248

Open
rhegde2 opened this issue Nov 26, 2024 · 3 comments
Open

CPU and Memory full on Harbor database server #21248

rhegde2 opened this issue Nov 26, 2024 · 3 comments

Comments

@rhegde2
Copy link

rhegde2 commented Nov 26, 2024

Hi Team,

We are using Harbor Version v2.9.1

When we trigger the image scan, we are experiancing sudden increase in number of database connections which inturn uses most of the CPU and Memory. It turns the DB server to hung state.

We tried increasing the CPU and RAM, and no luck.

There is no error on Postgres logs, however it was showing lot of "UPDATE waiting" message during the issue.

Below updates were running during the activity


UPDATE TAK

UPDATE "schedule" SET "revision"

UPDATE "repository" SET "pull_count" = "pull_count" + $1, "update_time" = $2 WHERE "repository_id" IN ( SELECT T0."repository_id" FROM "repository" T0 WHERE T0."repository_id" = $3;


Kindly suggest.

@chlins
Copy link
Member

chlins commented Nov 28, 2024

Could you provide more detailed data such as screenshot of the monitoring, harbor logs?

@stonezdj
Copy link
Contributor

stonezdj commented Dec 2, 2024

Suggest upgrading to the latest Harbor 2.12.0 because there are lots of performance improvements after v2.9.0. Is there any repository which has too many artifact or tags (>1000) ?

@chlins
Copy link
Member

chlins commented Dec 3, 2024

@rhegde2 Did you change any environment variables manually? the pull count updation should be async by default since v2.5, related PR: #16107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants