fix(replication): omni sequential send and read#967
Open
meskill wants to merge 1 commit into
Open
Conversation
meskill
force-pushed
the
push-tmpxoryqppmp
branch
from
d395b91 to
2cc4e22
Compare
meskill
force-pushed
the
fix/replication_send_order
branch
from
bb21097 to
7eaa24e
Compare
Contributor
|
Found 1 test failure on Blacksmith runners: Failure
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
1 participant
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.
"fix" for the #924 that trades latency to the lower changes of cross-shard deadlocks for the same row update for the omni tables.