Database / ScyllaDB Interview questions
What happens when a wide partition forms in ScyllaDB?
A wide partition occurs when a single partition key accumulates an unusually large number of rows or a very large amount of data, often from a low-cardinality key or unbounded time-series growth without bucketing. Because a partition is the unit that a single set of replicas must serve, the node(s) owning that partition end up doing disproportionate work.
Symptoms include elevated read and compaction latency for that specific partition, larger memtable and SSTable footprints concentrated on fewer nodes, and in extreme cases, timeouts when scanning the partition or during repair, since a wide partition takes longer to stream and validate. Monitoring tools flag large partition warnings so they can be caught before becoming critical. The fix is schema-level: bucket the partition key by a natural time window or hash suffix so what was one unbounded partition becomes many bounded ones spread across the cluster.
More Related questions...
