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

[VAULT-21623] Close rate-limit client purge goroutines when sealing #24108

Merged
merged 3 commits into from
Nov 15, 2023

Conversation

davidadeleon
Copy link
Contributor

This PR fixes a goroutine leak when using rate-limit quotas. When using rate-limit quotas, a goroutine is started per quota to check at a set interval whether or not we can remove a client from being blocked. When Vault would undergo a state-change that required sealing, Vault was not closing these purge goroutines. When unsealing Vault would re-initialize the rate-limit quotas starting a new set of goroutines, leaking the old ones.

@davidadeleon davidadeleon requested a review from a team November 13, 2023 14:40
@davidadeleon davidadeleon added this to the 1.13.11 milestone Nov 13, 2023
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Nov 13, 2023
@davidadeleon davidadeleon added backport/1.13.x and removed hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed labels Nov 13, 2023
Copy link

Build Results:
All builds succeeded! ✅

@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Nov 13, 2023
Copy link

CI Results:
All Go tests succeeded! ✅

Copy link
Contributor

@ccapurso ccapurso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants