-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release-22.2: server: retry ambiguous kv/sql operations on node startup #100463
Merged
aliher1911
merged 3 commits into
cockroachdb:release-22.2
from
aliher1911:backport22.2-97710
Apr 27, 2023
Merged
release-22.2: server: retry ambiguous kv/sql operations on node startup #100463
aliher1911
merged 3 commits into
cockroachdb:release-22.2
from
aliher1911:backport22.2-97710
Apr 27, 2023
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
In TestClusters with more than 4 nodes, wait for full replication doesn't take updated config into account. This commit adds new check that zone config was propagated prior to making replication state checks. Epic: none Release note: None
aliher1911
changed the title
testutil: zone config propagation wait for test cluster
server: retry ambiguous kv/sql operations on node startup
Apr 4, 2023
erikgrinaker
changed the title
server: retry ambiguous kv/sql operations on node startup
release-22.2: server: retry ambiguous kv/sql operations on node startup
Apr 21, 2023
aliher1911
force-pushed
the
backport22.2-97710
branch
8 times, most recently
from
April 25, 2023 17:36
4c7a842
to
fcbf4b7
Compare
Previously, nodes could fail on startup if node itself was needed to restore quorum on ranges. This problem was caused by circuit breaker failing fast on live node when talking back to restarting node instead of waiting for raft operation to run again (and succeed). This PR adds explicit retries and also adds assertions enabled in race build that would fire if startup reaches dist sender or internal sql executor without wrapping it in startup retry helper. Release note: None
We need to have the `RunIdempotentWithRetry` calls abort if the surrounding server shuts down prematurely. This happens most frequently in tests that fail for another reason; and also in multitenancy tests with multiple tenant server side-by-side. Release note: None
aliher1911
force-pushed
the
backport22.2-97710
branch
from
April 25, 2023 19:36
fcbf4b7
to
89855c8
Compare
TestTransientClusterSimulateLatencies is unrelated to backport and are flaking on the branch with the same error previously. |
@tbg this is a backport PR |
tbg
approved these changes
Apr 27, 2023
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.
In TestClusters with more than 4 nodes, wait for full replication
doesn't take updated config into account.
This commit adds new check that zone config was propagated prior to
making replication state checks.
Epic: none
Release note: None
Backport 2/2 commits from #97710.
/cc @cockroachdb/release
Previously, nodes could fail on startup if node itself was needed to restore quorum on ranges. This problem was caused by circuit breaker failing fast on live node when talking back to restarting node instead of waiting for raft operation to run again (and succeed).
This PR adds explicit retries and also adds assertions enabled in race build that would fire if startup reaches dist sender or internal sql executor without wrapping it in startup retry helper.
Release note: None
Fixes #74714
Includes fix #100583
Release justification: fixes a stability issue during node restarts