[3.2] Add --http-max-in-flight-requests to http_plugin option #561
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
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.
Backport EOSIO/eos#9431, resolve #431.
Notes about backport: current http_plugin.cpp was already ahead of EOSIO/eos#9431 and the PR had several commits going back and forth changes. Those made cherry-picking all the commits impossible. The first main commit was cherry-picked. The remaining ones were manually pulled in.
From original PR:
Added a new option for 'http-plugin':
http-max-in-flight-requests. It restricts the maximum requests the flight can hold if--http-max-in-flight-requests= positive number. If the limit exceeds, it sends a 429 error to the client. if --http-max-in-flight-requests= -1, there is no limit so the feature is turned off. It protects non-producingnodeosagainst the flood of requests when it cannot get new blocks.