chore(dashmate): limit concurrent state transition checks - #1824
Merged
Conversation
lklimek
previously approved these changes
Apr 22, 2024
lklimek
previously approved these changes
Apr 22, 2024
QuantumExplorer
approved these changes
Apr 24, 2024
QuantumExplorer
approved these changes
Apr 24, 2024
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.
Issue being fixed or feature implemented
To protect Drive from overwhelming number of check tx ABCI calls in case of stress testing or an attack, we need limit max concurrent check tx calls in Tenderdash dashpay/tenderdash#775
What was done?
platform.drive.tenderdash.mempool.maxConcurrentCheckTxoption to dashmateHow Has This Been Tested?
Broadcasting transactions to local network
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only