Relationship · Vulnerable To
Source: Workload·Target: Failure Mode
Summary
High-throughput OLTP workloads are vulnerable to hot shard problems when the shard key is a sequential ID or timestamp, concentrating all new writes on the highest-range shard.
Evidence
- ·hot_shard_unbalanced_writes triggers on sequential/timestamp shard keys for write-heavy workloads (failure_modes/hot_shard_unbalanced_writes.yaml)
- ·high_throughput_oltp peaks at 25k rps with a 5x spike multiplier (workloads/high_throughput_oltp.yaml)
Evidence grounding
Grounded, 2 supporting itemsHigh write rates on a monotonic shard key concentrate all writes on the current shard.