refactor(core-transaction-pool): better locking #3802
Merged
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.
Summary
Follow-up to #3800
New general-purpose
Lock
class is added tocore-kernel
utils to facilitate pool synchronization:In general this kind of locking is traditionally used in databases. Read-only transactions can run in parallel, write transactions require all read-only transactions to finish and then lock database until finished. Technique itself is more general and can be applied in non-database scenarios.
Several synchronization issues are fixed in pool:
Checklist