Go to file
Aparna Naik 19d4f1b087 CEP-45: Incremental Repair integration w/Mutation Tracking
Implement mutation tracking repair as a new repair task that replaces
Merkle tree validation and streaming for tracked keyspaces. Instead of
building hash trees and comparing data, MutationTrackingSyncCoordinator
sends MT_SYNC_REQ to all participants to collect their witnessed offsets,
then waits for background offset broadcasts to confirm all replicas have
reconciled to those target offsets.

Key changes:

- Add MutationTrackingIncrementalRepairTask that creates per-range
  MutationTrackingSyncCoordinator instances and blocks until all
  shards reach the target reconciled offsets or timeout.

- Add MT_SYNC_REQ/MT_SYNC_RSP verbs and MutationTrackingSyncRequest/
  MutationTrackingSyncResponse messages for the repair protocol to
  establish a happens-before relationship between repair start and
  offset collection.

- RepairCoordinator.create() factory method snapshots TCM state to
  decide whether to use mutation tracking repair and flips incremental
  to false (skipping anti-compaction) when MT is active without
  migration.

- Support mutation tracking migration: during untracked->tracked
  migration, run incremental repair first (for pre-migration data),
  then MT sync. KeyspaceMigrationInfo validates that repair ranges
  don't partially overlap pending migration ranges and routes
  streaming/SSTable finalization through the correct tracked vs
  untracked path.

- Temporarily route read repair mutations through the untracked write
  path during migration by adding isReadRepair flag to Mutation and
  bypassing migration routing checks in ReadRepairVerbHandler and
  CassandraKeyspaceWriteHandler. This is a stopgap; CASSANDRA-21252
  will roll back this approach and handle read repair properly.

- Add offset collection APIs to CoordinatorLog, Node2OffsetsMap, and
  Shard for computing union and intersection of witnessed offsets
  scoped to specific participant host IDs (supporting --force with
  dead node exclusion).

- Add configurable mutation_tracking_sync_timeout (default 2m) with
  JMX get/set on StorageServiceMBean.

- Fix ActiveRepairService to use tryFailure() instead of setFailure()
  to avoid double-completion exceptions during concurrent repair
  failures.

Co-Authored-By: Ariel Weisberg <aweisberg@apple.com>
2026-04-14 11:48:19 -04:00
.build Migrate all nodetool commands from airline to picocli 2025-07-26 18:19:18 +02:00
.circleci Migrate sstableloader code to its own tools directory and artifact 2025-05-18 12:35:52 -05:00
.github Add pull request template and modify README to include Jira and mailing list link 2022-09-21 09:10:28 +02:00
.jenkins Migrate sstableloader code to its own tools directory and artifact 2025-05-18 12:35:52 -05:00
bin Merge branch 'cassandra-5.0' into trunk 2025-07-31 09:22:44 +02:00
ci Implementation of Transactional Cluster Metadata as described in CEP-21 2023-11-24 10:26:08 +00:00
conf Merge branch 'cassandra-5.0' into trunk 2025-07-31 09:22:44 +02:00
debian Prepare debian changelog for 5.0.5 2025-07-31 11:40:54 +02:00
doc Improve sstableloader documentation for SSL configuration 2025-08-08 08:45:58 +02:00
examples Provide keystore_password_file and truststore_password_file options to read credentials from a file 2025-03-04 12:33:41 +01:00
ide Add testing of consensus live migration to simulator 2025-07-16 11:31:54 -04:00
lib Accord: PreLoadContext must properly and consistently support ranges 2025-04-17 11:59:50 -07:00
modules Avoid cache modification reentrancy when cancelling loads 2025-08-07 12:45:05 +01:00
pylib Fix test failure: cqlshlib.test.test_cqlsh_output.TestCqlshOutput::test_describe_schema_output 2025-08-13 16:19:15 -05:00
redhat Migrate sstableloader code to its own tools directory and artifact 2025-05-18 12:35:52 -05:00
src CEP-45: Incremental Repair integration w/Mutation Tracking 2026-04-14 11:48:19 -04:00
test CEP-45: Incremental Repair integration w/Mutation Tracking 2026-04-14 11:48:19 -04:00
tools Merge branch 'cassandra-5.0' into trunk 2025-07-31 09:22:44 +02:00
.asf.yaml enrich .asf.yaml 2024-08-23 10:48:15 +02:00
.gitignore Add more resources to .gitignore after CASSANDRA-19915 2025-03-14 16:25:54 +01:00
.gitmodules Ninja fix .gitmodules 2025-07-16 12:50:19 -04:00
.snyk Merge branch 'cassandra-5.0' into trunk 2025-04-02 12:11:24 +02:00
CASSANDRA-14092.txt Default to nb instead of nc for sstable formats 2023-11-13 09:26:11 +01:00
CHANGES.txt Add support for counters to mutation tracking 2026-01-16 16:28:58 +00:00
CONTRIBUTING.md CEP-15 (C*): Messaging and storage engine integration 2025-04-17 11:59:47 -07:00
LICENSE.txt Merge branch 'cassandra-3.11' into cassandra-4.0 2023-08-31 22:39:56 +02:00
NEWS.txt Automated Repair Inside Cassandra for CEP-37 2025-04-23 11:04:36 -05:00
NOTICE.txt Merge branch 'cassandra-3.11' into cassandra-4.0 2023-02-22 10:25:08 -06:00
README.asc Merge branch 'cassandra-5.0' into trunk 2025-08-08 08:18:05 +02:00
TESTING.md Improve and clean up documentation and fix typos 2023-01-26 14:42:47 +01:00
build-shaded-dtest-jar.sh Merge branch 'cassandra-3.11' into trunk 2021-04-19 17:39:10 +02:00
build.properties.default Merge branch 'cassandra-5.0' into trunk 2024-09-16 15:53:25 -04:00
build.xml bump version 2025-08-05 14:33:59 +02:00
relocate-dependencies.pom Upgrade maven-shade-plugin to 3.4.1 to fix shaded dtest JAR build 2023-03-14 15:57:14 -05:00

README.asc

Apache Cassandra
-----------------

Apache Cassandra is a highly-scalable partitioned row store. Rows are organized into tables with a required primary key.

https://cwiki.apache.org/confluence/display/CASSANDRA2/Partitioners[Partitioning] means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster.

https://cwiki.apache.org/confluence/display/CASSANDRA2/DataModel[Row store] means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

For more information, see http://cassandra.apache.org/[the Apache Cassandra web site].

Issues should be reported on https://issues.apache.org/jira/projects/CASSANDRA/issues/[The Cassandra Jira].

Requirements
------------
- Java: see supported versions in build.xml (search for property "java.supported").
- Python: for `cqlsh`, see `bin/cqlsh` (search for function "is_supported_version").


Getting started
---------------

This short guide will walk you through getting a basic one node cluster up
and running, and demonstrate some simple reads and writes. For a more-complete guide, please see the Apache Cassandra website's https://cassandra.apache.org/doc/latest/cassandra/getting_started/index.html[Getting Started Guide].

First, we'll unpack our archive:

  $ tar -zxvf apache-cassandra-$VERSION.tar.gz
  $ cd apache-cassandra-$VERSION

After that we start the server. Running the startup script with the -f argument will cause
Cassandra to remain in the foreground and log to standard out; it can be stopped with ctrl-C.

  $ bin/cassandra -f

Now let's try to read and write some data using the Cassandra Query Language:

  $ bin/cqlsh

The command line client is interactive so if everything worked you should
be sitting in front of a prompt:

----
Connected to Test Cluster at localhost:9160.
[cqlsh 6.3.0 | Cassandra 5.0-SNAPSHOT | CQL spec 3.4.8 | Native protocol v5]
Use HELP for help.
cqlsh>
----

As the banner says, you can use 'help;' or '?' to see what CQL has to
offer, and 'quit;' or 'exit;' when you've had enough fun. But lets try
something slightly more interesting:

----
cqlsh> CREATE KEYSPACE schema1
       WITH replication = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };
cqlsh> USE schema1;
cqlsh:Schema1> CREATE TABLE users (
                 user_id varchar PRIMARY KEY,
                 first varchar,
                 last varchar,
                 age int
               );
cqlsh:Schema1> INSERT INTO users (user_id, first, last, age)
               VALUES ('jsmith', 'John', 'Smith', 42);
cqlsh:Schema1> SELECT * FROM users;
 user_id | age | first | last
---------+-----+-------+-------
  jsmith |  42 |  john | smith
cqlsh:Schema1>
----

If your session looks similar to what's above, congrats, your single node
cluster is operational!

For more on what commands are supported by CQL, see
https://cassandra.apache.org/doc/trunk/cassandra/developing/cql/index.html[the CQL reference]. A
reasonable way to think of it is as, "SQL minus joins and subqueries, plus collections."

Wondering where to go from here?

  * Join us in #cassandra on the https://s.apache.org/slack-invite[ASF Slack] and ask questions.
  * Subscribe to the Users mailing list by sending a mail to
    user-subscribe@cassandra.apache.org.
  * Subscribe to the Developer mailing list by sending a mail to
    dev-subscribe@cassandra.apache.org.
  * Visit the http://cassandra.apache.org/community/[community section] of the Cassandra website for more information on getting involved.
  * Visit the http://cassandra.apache.org/doc/latest/development/index.html[development section] of the Cassandra website for more information on how to contribute.