Skip to content
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

kvserver: propagate ReplicaUnavailableError from intent resolution #105816

Merged

Conversation

erikgrinaker
Copy link
Contributor

@erikgrinaker erikgrinaker commented Jun 29, 2023

If intent resolution attempted to access txn info on a different range, and hit a poisoned latch because that range had lost quorum, the returned error would incorrectly claim that the range with the intent was unavailable rather than the range that had lost quorum. This patch correctly propagates the ReplicaUnavailableError from the other range.

Resolves #105798.
Resolves #102936.
Epic: none

Release note: None

@erikgrinaker erikgrinaker requested review from tbg and a team June 29, 2023 14:44
@erikgrinaker erikgrinaker self-assigned this Jun 29, 2023
@erikgrinaker erikgrinaker requested a review from a team as a code owner June 29, 2023 14:44
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@pav-kv
Copy link
Collaborator

pav-kv commented Jun 29, 2023

Is this the same issue as #102936?

If intent resolution attempted to access txn info on a different range,
and hit a poisoned latch because that range had lost quorum, the
returned error would incorrectly claim that the range with the intent
was unavailable rather than the range that had lost quorum. This patch
correctly propagates the `ReplicaUnavailableError` from the other range.

Epic: none
Release note: None
@erikgrinaker erikgrinaker force-pushed the replica-unavailable-intent-resolution branch from 0951e32 to 3a68186 Compare June 29, 2023 21:18
@erikgrinaker erikgrinaker added backport-22.2.x backport-23.1.x Flags PRs that need to be backported to 23.1 labels Jun 29, 2023
@erikgrinaker
Copy link
Contributor Author

Is this the same issue as #102936?

Yep, thanks for the pointer.

@erikgrinaker
Copy link
Contributor Author

bors r+

@craig
Copy link
Contributor

craig bot commented Jun 29, 2023

Build succeeded:

@blathers-crl
Copy link

blathers-crl bot commented Jun 29, 2023

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 3a68186 to blathers/backport-release-22.2-105816: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 22.2.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-23.1.x Flags PRs that need to be backported to 23.1 db-cy-23
Projects
None yet
4 participants