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 failure to periodically flush after dropping a Db instance #1159

Merged
merged 17 commits into from
Sep 10, 2020

Conversation

spacejam
Copy link
Owner

this is the ongoing workspace for fixing the bug found in #1152

@soro
Copy link
Contributor

soro commented Sep 4, 2020

I have to say that I can't find another obvious deadlock that would lead to an issue in this particular scenario - the interface is such though that it is pretty easy to deadlock if the thread processing the subscription does anything else involving subscriptions, such as try to subscribe to another prefix. Maybe it would be best just to never block on the sending side and just use try_send? That or simply use a concurrent map as the registry so those locks don't have to be taken while sending is going on.

@spacejam spacejam merged commit 31765d3 into master Sep 10, 2020
@spacejam spacejam deleted the tyler_subscriber_send_lock branch September 10, 2020 09:58
@spacejam spacejam changed the title debug subscription + transaction deadlock fix failure to periodically flush after dropping a Db instance Sep 10, 2020
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.

None yet

2 participants