Tagged articles
5 articles
Page 1 of 1

How Single-Leader Replication Handles Write Conflicts: Strategies and Insights

This article examines write conflicts in single-leader replication, comparing exclusive and shared data, exploring uniqueness constraints, async replication delays, and various conflict‑resolution techniques such as unique indexes, bitmap mapping, LWW ordering, and multi‑version control for collaborative editing.

ConsistencyDistributed SystemsReplication
0 likes · 9 min read
How Single-Leader Replication Handles Write Conflicts: Strategies and Insights
Xiaolei Talks DB
Xiaolei Talks DB
Jul 21, 2021 · Databases

Optimistic vs Pessimistic Transactions in TiDB: 10x Performance Boost

This article compares TiDB's optimistic and pessimistic transaction models through a real‑world high‑concurrency write‑conflict scenario, showing how pessimistic locking can achieve over ten times higher throughput than optimistic retries.

Database ConcurrencyOptimistic TransactionPessimistic Transaction
0 likes · 14 min read
Optimistic vs Pessimistic Transactions in TiDB: 10x Performance Boost
360 Tech Engineering
360 Tech Engineering
Aug 10, 2020 · Databases

TiDB Cluster Write‑Write Conflict Investigation and Resolution

This article analyzes a TiDB cluster performance incident where QPS dropped and duration spiked due to write‑write conflicts, detailing the monitoring data, root‑cause investigation of server‑busy and scheduler latch issues, and the attempted mitigation steps such as enabling txn‑local‑latches and adjusting insert statements.

Cluster TroubleshootingDatabase operationsTiDB
0 likes · 10 min read
TiDB Cluster Write‑Write Conflict Investigation and Resolution
360 Zhihui Cloud Developer
360 Zhihui Cloud Developer
Aug 5, 2020 · Databases

How a TiDB Write Conflict Crashed a Cluster and What Fixed It

This article analyzes a TiDB production cluster outage caused by write‑write conflicts, walks through the monitoring data and log investigation, explains the underlying transaction model differences, and shares the step‑by‑step troubleshooting process that led to the final resolution.

Cluster TroubleshootingSchedulerTiDB
0 likes · 11 min read
How a TiDB Write Conflict Crashed a Cluster and What Fixed It