[ETCM-493] Increase eth_syncing ask timeout #878
Merged
Conversation
This file contains hidden or 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
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.
Description
During fast sync, the
FastSyncactor is busy and may take some time to respond to the ask call from theEthService. Our current ask timeout for that call is 100 milliseconds, so from time to time if there are many requests, the service will timeout.See #852.
Proposed Solution
To fix the issue now, we decided to increase the timeout because the actor eventually responds, it just takes more than 100 milliseconds.
A refactoring of all the sync-related actors is on the roadmap so it isn't worth to make an optimization for this
eth_syncingendpoint right now.Testing
See steps to reproduce in #852.