[master] Allow syncing of ds nodes if they kicked out of ds comm instead of rejoin from scrach #3896
+3
−2
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.
Description
A DS node is removed from the consensus because of not signing enough blocks or competition performs rejoins. This means it downloads complete persistence and syncs again which is a very time-consuming process. The fix is to allow the node to start syncing to join in the next epoch.
Backward Compatibility
Review Suggestion
Status
Implementation
Integration Test (Core Team)