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
TiDB executes point-get requests with non-clustered indexes in the following process:
Read index value
Lock index key
Lock handle key
An ideal process may be reading the index value from the locking response. But for RC mode, we only lock keys when they exist, there may be a lock-if-exist option for the pessimistic lock.
Another possible solution is the batch-point-get's style, locks index keys and handle keys in parallel, which does not follow a fixed locking order, and may be more risk of deadlock.
The text was updated successfully, but these errors were encountered:
Enhancement
TiDB executes point-get requests with non-clustered indexes in the following process:
An ideal process may be reading the index value from the locking response. But for RC mode, we only lock keys when they exist, there may be a lock-if-exist option for the pessimistic lock.
Another possible solution is the batch-point-get's style, locks index keys and handle keys in parallel, which does not follow a fixed locking order, and may be more risk of deadlock.
The text was updated successfully, but these errors were encountered: