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

GC causes outage on production Harbor deployment #20000

Open
nmcostello opened this issue Feb 20, 2024 · 3 comments
Open

GC causes outage on production Harbor deployment #20000

nmcostello opened this issue Feb 20, 2024 · 3 comments
Assignees

Comments

@nmcostello
Copy link

I posted this issue in the goharbor/harbor-helm#1708 in the harbor-helm repo.

Reposting here to see if we can get any traction on this issue.

@wy65701436
Copy link
Contributor

Per the information of the original issue, could you please explain why you reset these two values? 14 is not enough for a running harbor, by default, it's set to 900.

maxIdleConns: 4
maxOpenConns: 14

@nmcostello
Copy link
Author

@wy65701436
During normal load on our system, our core pods can scale to 80+ pods based on our HPAs. If I'm doing the math correctly, the docs say that each pod (core+exporter) can hold maxOpenConns meaning if we had it set to the default, when we scaled to 80 pods then our connections would be +70k connections. Unless I am misunderstanding something.

https://github.com/goharbor/harbor-helm/blob/main/values.yaml#L899

Copy link

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added the Stale label Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants