-
Notifications
You must be signed in to change notification settings - Fork 332
Fix gundeck leak #3136
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
Merged
Merged
Fix gundeck leak #3136
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
7b20bc7
fix: memory leak in Gundeck
isovector 4c2d060
chore: format
isovector 5baea96
fix: keep old retry logic in runRobust
isovector ae93c93
doc: changelog
isovector 941e139
Hi CI
e37ecca
chore: format
4a8c4ef
chore: hlint
isovector fcc9b8e
chore: format again
isovector fa9fce1
fix: cleanup redis threads
isovector e6143ea
empty push
isovector 16c3c46
Hi CI
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Fix a memory leak in `gundeck` when Redis is offline |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Essentially you say,
oncewas not working? Ifoncewas working, there should never have been a race for updating theMVar. Or rather, theMVarwould be swapped several times which could have been optimised by puttingswapMVarbelowonce. Or is there more to it which I haven't grasped in this case?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's bugging me is that I don't see the memory leak. After all pending Redis actions went through the (admittedly redundant)
swapMVar, no memory should be retained. Though, I do see that it seems fixed by this PR.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also don't see it, which is why I spent 16 hours digging through heap profiles before I tried changing the code 😊 . My best guess is that
onceisn't safe in a concurrent environment. It's implemented (indirectly) viamodifyMVar, which comes with this warning:which makes me think
onceis indeed the culprit. But I don't know!The other difference between the two logics is that HEAD will still call
runRedisinrunRobuston a known-bad connection, and it could be some of the janky pipelining in hedis is responsible for leaking the stacks here.