This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
[R4R] add timeout for catch up condition check with no peers #174
Conversation
This file contains 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
realuncle
approved these changes
Nov 9, 2022
unclezoro
approved these changes
Nov 9, 2022
5 tasks
5 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In fast sync mode, normally it needs at least 1 peer to be considered caught up.
There is a change that a node with the majority of voting power has no peers, it will never have changes to catch up and switch to consensus reactor, resulting in stopping the chain.
So we add a 10 minutes timeout to prevent this case.