-
-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: close REST API server before closing network #6061
Merged
Merged
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
Performance Report✔️ no performance regression detected Full benchmark results
|
dapplion
approved these changes
Oct 24, 2023
wemeetagain
approved these changes
Oct 24, 2023
🎉 This PR is included in v1.12.0 🎉 |
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.
Motivation
Some APIs depend on the network to be operational, e.g.
submitPoolAttestations
andpublishAggregateAndProofs
but the network itself has no dependency to the REST API server, hence it is better if we close the REST API server first and stop accepting new requests before starting to close the network.Errors that might happen due to current close sequence
Note that these errors are really rare in normal circumstances as the time between closing the network and the REST API server is usually just a few milliseconds but due to current libp2p issue #6053 this issue becomes more apparent.
Description
Close REST API server before closing network
The only reason I see why we would close the network first is that some APIs are still functional if they only rely on chain data but we are already closing the connections gracefully (#5786) which gives pending requests some time to complete.