How is the serial consistency level configured?

Serial consistency levels in DataStax Enterprise control lightweight transaction isolation. The consistency levels for lightweight transactions are shown in the following table.

Serial consistency levels

Level Description Usage


Achieves linearizable consistency for lightweight transactions by preventing unconditional updates.

This consistency level is for use only with lightweight transactions. Equivalent to How QUORUM is calculated.


Same as SERIAL but confined to a single data center. A conditional write must be written to the commit log and memtable on a quorum of replica nodes in the same datacenter.

Same as SERIAL but used to maintain consistency locally (within the single local datacenter). Equivalent to LOCAL_QUORUM.

For local consistency, which enforces serialization within the local datacenter, use:

  • LOCAL_SERIAL for LWT reads.


For global consistency, which enforces serialization across multiple datacenters, use:

  • SERIAL for LWT reads.

  • QUORUM and SERIAL for LWT writes.

Background information: The SERIAL consistency level defines the serial consistency level for the Paxos consensus of lightweight transactions. The learn phase uses a normal consistency level to define which read operations will be guaranteed to complete immediately if lightweight writes are occurring. The SERIAL consistency level is ignored for any query that is not a conditional update.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,