-
Notifications
You must be signed in to change notification settings - Fork 155
fix: numa container hangs occassionally when map panics #3179
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
Closed
Closed
Changes from 5 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
43d6f67
fix for numa stuck when map panics
vaibhavtiwari33 e7a05e6
merge: main
vaibhavtiwari33 d842537
fix linting
vaibhavtiwari33 d01660e
merge
vaibhavtiwari33 3f01e96
replace with while syntax
vaibhavtiwari33 47296da
make changes in all map types
vaibhavtiwari33 13fecbf
Merge branch 'main' into map-panic-fix
vaibhavtiwari33 4a2fc56
chore: review comments
yhl25 89c63df
add debugging logs
vaibhavtiwari33 be6a7f9
add debugging logs
vaibhavtiwari33 729b90f
Merge branch 'main' into map-panic-fix
vaibhavtiwari33 de6c50d
Remove debugging logs. Add a response sender map state to check befor…
vaibhavtiwari33 7c21dac
un comment clippy checks
vaibhavtiwari33 952ed4b
fix lint. fix clippy errors
vaibhavtiwari33 43c662a
Merge branch 'main' into map-panic-fix
vaibhavtiwari33 fbdea1c
Add similar fix for batch and stream
vaibhavtiwari33 952b307
Merge branch 'main' into map-panic-fix
vaibhavtiwari33 8d6da26
put back clippy
vaibhavtiwari33 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
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
Oops, something went wrong.
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.
replace the original loop with the
while let some(_)?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.
That will work but we do lose the original gRPC error that was received from the stream in that case.
Uh oh!
There was an error while loading. Please reload this page.
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.
One reason why we shouldn't do this:
would be to avoid processing a message that has already been removed and for which error has been broadcasted if we've encountered an error before.
We'll be spending time to acquire lock to the senders map to remove an entry that might not be there.
Uh oh!
There was an error while loading. Please reload this page.
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'll add a boolean state check behind the response sender map mutex so that we don't have to worry about this and can use your semanticThe abovementioned scenario would still play out with the mentioned semantics