Is 495 catchup timeout #2062
Merged
Is 495 catchup timeout #2062
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
olehnikolaiev
requested review from
DmytroNazarenko and
kladkogex
as code owners
kladkogex
approved these changes
Jan 3, 2025
DmytroNazarenko
approved these changes
Jan 3, 2025
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.
fixes https://github.com/skalenetwork/internal-support/issues/945
increase catchup timeout for sync nodes
make catchup timeouts configurable via new config fields "catchupTimeoutSec", "syncNodeCatchupTimeoutSec", "readJsonHeaderTimeoutSec", "syncNodeReadJsonHeaderTimeoutSec". default values are 30, 300, 6 and 300
tests - spin up an archive node for the mainnet chain and confirm it is able to catchup 0 block
no performance impact