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
current process
For RC isolation, TiDB currently sends a get request to judge whether the keys exists on the TiKV firstly, then sends a pessimistic lock request to TiKV if the key exists, It makes an additional rpc request.
what changed
We add a flag LockIfExists for pessimistic lock request and TiKV will check the flag to decide how to execute the lock process. TiDB only send a pessimistic lock request to TiKV. If the keys exist, TiKV locks the keys and return the values of the keys, else does nothing and return.
The text was updated successfully, but these errors were encountered:
Enhancement
current process
For RC isolation, TiDB currently sends a get request to judge whether the keys exists on the TiKV firstly, then sends a pessimistic lock request to TiKV if the key exists, It makes an additional rpc request.
what changed
We add a flag LockIfExists for pessimistic lock request and TiKV will check the flag to decide how to execute the lock process. TiDB only send a pessimistic lock request to TiKV. If the keys exist, TiKV locks the keys and return the values of the keys, else does nothing and return.
The text was updated successfully, but these errors were encountered: