-
Notifications
You must be signed in to change notification settings - Fork 120
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
Avoid deadlocks in the address book mutex #3244
Conversation
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 need to make a few fixes to this, mainly to await spawned tasks
10f7341
to
94b6f52
Compare
cf13a20
to
35d3b37
Compare
I've marked this PR and all its dependencies as a high priority, because this is a known bug that has actually happened before, and seems to still be happening. |
@teor2345 should this still be in draft and is it ready to be reviewed? |
This makes it more likely that peers will become ready.
94b6f52
to
4f13056
Compare
35d3b37
to
7c026cd
Compare
Rebased after the base #3191 was rebased 😅 |
@mpguerra yes it needs to be in draft, and yes it is ready to be reviewed. See my detailed answer here: #3191 (comment) |
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.
It looks good, i made a few comments but nothing really blocking imho.
Co-authored-by: Alfredo Garcia <oxarbitrage@gmail.com>
Motivation
zebra-network
keeps on having hard-to-diagnose hangs. These hangs could be happening because theAddressBook
uses a threaded mutex, which blocks the executor, and all async tasks scheduled on the same thread.Solution
Closes #3240
Review
@dconnolly can review this PR.
This is urgent because syncs are very slow, and #3191 or #3244 should help fix that.
It's based on PR #3191.Reviewer Checklist
Follow Up Work