add p2p.sync.onlyreqtostatic
flag to p2p flags
#11011
Merged
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.
This PR adds a
p2p.sync.onlyreqtostatic
flag to op-node so that when enabled,RequestL2Range
will only forward requests to static peers.This is handy for new nodes to increase the success rate for
checkForGapInUnsafeQueue
, otherwise it often happens that bad peers received the request(peers race to handle the request by receiving frompeerRequests
channel) and thus report "failed to check for unsafe L2 blocks to sync".This flag is especially useful for opstack instances with large batcher submit interval(e.g, 12h).
(The big flag diff is caused by goformat, only a new flag
SyncOnlyReqToStaticName
was added)