Skip to content

AxonOps — AI-Native Control Plane for Open Source Data Platforms

Cassandra Consistency Levels Reference

This page provides quick-reference tables for Cassandra consistency levels. For detailed explanations of how consistency works, see Consistency.


LevelReplicas RequiredDescriptionAvailability
ANY1 (including hints)Write succeeds if any node (including coordinator) acknowledges. May store as hint only.Highest
ONE1Single replica must acknowledgeHigh
TWO2Two replicas must acknowledgeMedium
THREE3Three replicas must acknowledgeMedium
QUORUMRF/2 + 1 (global)Majority of all replicas across all datacentersMedium
LOCAL_ONE1 (local DC)Single replica in coordinator's datacenterHigh
LOCAL_QUORUMlocal_RF/2 + 1Majority in coordinator's datacenter onlyHigh
EACH_QUORUMlocal_RF/2 + 1 per DCMajority in every datacenter (each DC's RF used independently)Low
ALLRF (all replicas)Every replica must acknowledgeLowest

LevelReplicas ContactedDescriptionAvailability
ONE1Single replica respondsHighest
TWO2Two replicas respond; newest returnedHigh
THREE3Three replicas respond; newest returnedMedium
QUORUMRF/2 + 1 (global)Majority of all replicas; newest returnedMedium
LOCAL_ONE1 (local DC)Single replica in coordinator's datacenterHighest
LOCAL_QUORUMlocal_RF/2 + 1Majority in coordinator's datacenter; newest returnedHigh
ALLRF (all replicas)All replicas respond; newest returnedLowest

EACH_QUORUM

EACH_QUORUM is write-only. It is not supported for read operations.


Lightweight transactions use separate consistency levels for the Paxos consensus phase.

LevelScopeDescription
SERIALAll datacentersPaxos consensus across all replicas globally
LOCAL_SERIALLocal datacenterPaxos consensus within coordinator's datacenter only

See Lightweight Transactions for CQL syntax and Paxos for architecture details.


Formula: QUORUM = floor(RF / 2) + 1

Replication FactorQUORUMCan Tolerate Failures
110
220
321
431
532
642
743

For a cluster with RF=3 per datacenter (total RF=6 across 2 DCs):

LevelReplicas RequiredCross-DC WaitDC Failure Tolerance
ONE1 (any DC)NoYes
LOCAL_ONE1 (local DC)NoYes
QUORUM4 (any DCs)YesNo
LOCAL_QUORUM2 (local DC)NoYes
EACH_QUORUM2 per DCYesNo
ALL6 (all DCs)YesNo

Recommended for Multi-DC

LOCAL_QUORUM is recommended for most multi-datacenter deployments. It provides strong consistency within each datacenter. Datacenter failure tolerance depends on client placement; clients must be able to reach another DC to fail over.


Heuristic: R + W > RF generally provides strong consistency (reads see latest writes) under normal operation. This assumes no concurrent failures affecting the same replica set and does not account for edge cases like ANY writes or transient divergence.

Write CLRead CLRF=3Strong?Notes
QUORUMQUORUM2+2=4 > 3YesStandard strong consistency
ONEALL1+3=4 > 3YesWrite-heavy workloads
ALLONE3+1=4 > 3YesRead-heavy workloads
LOCAL_QUORUMLOCAL_QUORUM2+2=4 > 3YesPer-datacenter strong consistency
ONEONE1+1=2 < 3NoEventual consistency
ONEQUORUM1+2=3 = 3NoNot strictly greater

Nodes DownONEQUORUMALL
0
1
2
Failure ScenarioLOCAL_QUORUMQUORUMEACH_QUORUM
1 node in local DC
2 nodes in local DC✅*
Entire remote DC down

*QUORUM may succeed if remote DC nodes compensate.


LevelSingle DCMulti-DCNotes
ONE~1-2ms~1-2msFastest
LOCAL_ONELowLowSame as ONE for local
QUORUMLowHigher (cross-DC)Cross-DC round trip in multi-DC
LOCAL_QUORUMLowLowNo cross-DC wait
EACH_QUORUMN/AHigher (cross-DC)Waits for slowest DC
ALLHigherHigher (cross-DC)Waits for slowest replica

Actual latencies are workload-, topology-, and hardware-dependent.


RequirementRecommended Write CLRecommended Read CL
Strong consistency, single DCQUORUMQUORUM
Strong consistency, multi-DCLOCAL_QUORUMLOCAL_QUORUM
Global strong consistencyQUORUMQUORUM
Maximum throughputONEONE
Write-heavy, strong readsONEALL
Read-heavy, strong writesALLONE
Time-series / metricsLOCAL_ONELOCAL_ONE
Compare-and-set (LWT)N/A (use IF clause)N/A