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

Fix goroutine leak caused by updating rate quotas #11371

Merged
merged 4 commits into from
Apr 16, 2021

Conversation

ncabatoff
Copy link
Collaborator

@ncabatoff ncabatoff commented Apr 16, 2021

No description provided.

@vercel vercel bot temporarily deployed to Preview – vault April 16, 2021 13:47 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook April 16, 2021 13:47 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook April 16, 2021 14:27 Inactive
@vercel vercel bot temporarily deployed to Preview – vault April 16, 2021 14:27 Inactive
@ncabatoff ncabatoff requested a review from a team April 16, 2021 14:28
@ncabatoff ncabatoff added this to the 1.6.4 milestone Apr 16, 2021
@ncabatoff ncabatoff changed the title Make sure that when we modify a rate quota, we stop the existing goro… Fix goroutine leak caused by updating rate quotas Apr 16, 2021
@vercel vercel bot temporarily deployed to Preview – vault April 16, 2021 16:00 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook April 16, 2021 16:00 Inactive
@ncabatoff ncabatoff merged commit 74bd3ee into master Apr 16, 2021
@ncabatoff ncabatoff deleted the fix-setquota-goroutine-leak branch April 16, 2021 18:00
ncabatoff added a commit that referenced this pull request Apr 16, 2021
Make sure that when we modify a rate quota, we stop the existing goroutine before starting the new one.
ncabatoff added a commit that referenced this pull request Apr 16, 2021
Make sure that when we modify a rate quota, we stop the existing goroutine before starting the new one.
ncabatoff added a commit that referenced this pull request Apr 16, 2021
Make sure that when we modify a rate quota, we stop the existing goroutine before starting the new one.
ncabatoff added a commit that referenced this pull request Apr 16, 2021
…) (#11380)

Make sure that when we modify a rate quota, we stop the existing goroutine before starting the new one.
sink, _ := metrics.New(metrics.DefaultConfig(""),
&metrics.BlackholeSink{})
conf := metrics.DefaultConfig("")
conf.EnableRuntimeMetrics = false
Copy link
Member

Choose a reason for hiding this comment

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

Was this intentionally disabled?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, to avoid it creating a goroutine that interferes with the leak test. I believe BlackholeSink is only used in tests.

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

Successfully merging this pull request may close these issues.

3 participants