Hi Team, In Cassandra 3.x, Anti-compaction is performed after repair (incremental or full). Repair does not have any way to bypass anti-compaction (if not running sub range repair with -st & -et). Here is a jira ticket.
https://issues.apache.org/jira/browse/CASSANDRA-11511 I am facing 100% disk utilization when running repair -pr after upgrading Cassandra from 2.1.16 to 3.11.2. I have a 2TB disk & 1.35TB is used. There are multiple keyspaces and each keyspace is having multiple tables. One of the sstable has huge data. Here is the details of it : Keyspace, tabel & SStable have 1.3TB, 730GB, 270 GB of data. I have following questions : 1. Is there any way to disable anti-compaction after repair is completed ? 2. After what stage, anti-compaction is performed after repair ? 3. Any other suggestions? Regards, Pushpendra
