You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…wait queue
Summary:
Prior to this revision, if two single tablet transactions arrived to the same WaitQueue instance, we
would try to store their WaiterData info in a map indexed by transaction ID, which for these
transactions was always Nil. Therefore we would overwrite the previous WaiterData each time and the
overwritten waiters would fail.
This revision improves the handling of single tablet waiters to handle multiple single tablet
waiters at the same tablet. We periodically send a retryable error to the client of a waiting single
tablet transaction to ensure we do not continue tracking these operations indefinitely in case the
client fails. Live clients will receive this status after FLAGS_force_single_shard_waiter_retry_ms
and will resend the request to the tablet..
Test Plan:
ybd --cxx-test pgwrapper_pg_pessimistic_locking-test
ybd --java-test org.yb.pgsql.TestPgPessimisticLockingRegress
Reviewers: sergei, pjain
Reviewed By: pjain
Subscribers: mbautin
Differential Revision: https://phabricator.dev.yugabyte.com/D19553
We currently do not properly handle the case where multiple transactions are waiting at the same tablet
The text was updated successfully, but these errors were encountered: