kv: serializable non-locking reads should not block on exclusive locks #117627
Labels
A-kv-transactions
Relating to MVCC and the transactional model.
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
O-support
Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs
P-3
Issues/test failures with no fix SLA
T-kv
KV Team
kv.lock.exclusive_locks_block_non_locking_reads.enabled
dictates whether exclusive locks block serializable non-locking reads. It defaults to true for compatibility reasons, but we'd like for it to default to false (and then be removed).To address this, we'll likely need to address #91417 first to avoid regressions in workloads like YCSB.
Jira issue: CRDB-35279
The text was updated successfully, but these errors were encountered: