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

Unsubscribe slow chain head subscribers #6974

Closed
wants to merge 3 commits into from
Closed

Conversation

Stebalien
Copy link
Member

This way, slow readers can just "resubscribe" when they're able to catch up. That way, a single slow leader doesn't block all notifications.

fixes #6883, #6947

@Stebalien Stebalien requested a review from a team as a code owner August 2, 2021 21:30
@Stebalien Stebalien marked this pull request as draft August 2, 2021 21:30
@Stebalien

This comment has been minimized.

The reader can just re-subscribe when they're ready to catch up. This
prevents a slow reader from bogging down the entire system.
@Stebalien Stebalien marked this pull request as ready for review August 3, 2021 17:59
@Stebalien
Copy link
Member Author

Ok, so it looks like this is revealing a bug in the events system as it doesn't correctly play "catchup".

@Stebalien
Copy link
Member Author

My diagnosis is correct, but fixing this is going to be slightly painful.

@Stebalien
Copy link
Member Author

Closing in favor of #7000.

@Stebalien Stebalien closed this Aug 11, 2021
@Stebalien Stebalien deleted the fix/slow-sub branch August 25, 2021 19:38
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.

Lotus' api ChainNotify sometimes keeps blocking
1 participant