Retry mechanism when getting a broadcasted block fail on all peers #4271
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
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
…-Trintinalia/besu into 3955-besu-stop-importing
Signed-off-by: Gabriel Trintinalia <[email protected]>
…ancestors of Block Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
…ing pending block to the list Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Gabriel Trintinalia <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
RetryingGetBlockFromPeersTask had a problem that prevented to complete when all the peers were tried without success, and that also had the consequence to not removing the failed requested block for the internal caches in BlockPropagationManager, that could cause a stall since that block will to be tried to be retrieved again. Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
…d in RetryingGetBlockFromPeers Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
fab-10
changed the title
Signed-off-by: Fabio Di Fabio <[email protected]>
Signed-off-by: Fabio Di Fabio <[email protected]>
# Conflicts: # CHANGELOG.md # ethereum/eth/src/test/java/org/hyperledger/besu/ethereum/eth/sync/AbstractBlockPropagationManagerTest.java
jflo
approved these changes
Aug 19, 2022
| if (!config.getBlockPropagationRange().contains(distanceFromChainHead)) { | ||
| debugLambda( | ||
| LOG, | ||
| "Not retrying to get block {} since we are too far from local chain head {}", |
There was a problem hiding this comment.
Is this a good place to suggest the user to start over with a checkpoint sync? If we got here during a backwards sync, that might be the only way to recover.
There was a problem hiding this comment.
Not sure I got this, backward sync does not run along with BlockPropagationManager
…ck data structures Signed-off-by: Fabio Di Fabio <[email protected]>
|
@jflo added a timeout and did some refactoring in the last commit, do you mind to review again? |
macfarla
approved these changes
Aug 26, 2022
garyschulte
pushed a commit
to garyschulte/besu
that referenced
this pull request
Sep 7, 2022
…yperledger#4271) Signed-off-by: Fabio Di Fabio <[email protected]>
garyschulte
pushed a commit
to garyschulte/besu
that referenced
this pull request
Sep 7, 2022
…yperledger#4271) Signed-off-by: Fabio Di Fabio <[email protected]>
garyschulte
pushed a commit
to garyschulte/besu
that referenced
this pull request
Sep 7, 2022
…yperledger#4271) Signed-off-by: Fabio Di Fabio <[email protected]> Signed-off-by: garyschulte <[email protected]>
eum602
pushed a commit
to lacchain/besu
that referenced
this pull request
Nov 3, 2023
…yperledger#4271) Signed-off-by: Fabio Di Fabio <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR description
Currently even if we use the RetryingGetBlockFromPeers, that tries to download the block, checking every peer in turn, if all peers fail, the retrieval is not repeated, unless the block is announced again.
This PR improve the block propagation manager, to repeat the download of a block, until some conditions apply: it is still not imported and the distance from the local head is within configured range.
Fixed Issue(s)
relates to #3955
Documentation
doc-change-requiredlabel to this PR ifupdates are required.
Changelog