Do region flush in Region::handleWriteRaftCmd (#542) #551
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.
cherry-pick #542 to release-3.1
Region::handleWriteRaftCmd
, so that it be protected byRegion::mutex
andRegion::predecode_mutex
RegionTable::writeBlockByRegion
fromRegionTable:: flushRegion
, so thatwriteBlockByRegion
can be called directly fromRegion::handleWriteRaftCmd
. Note that we don't callflushRegion
directly because we try to avoid getting instance ofRegionTable
, some unnecessary check and print log. AsRegion::handleWriteRaftCmd
is very performance critical.