Some more info. Tried different GC strategies - no luck.
It only happens on large tables (more than 1 billion rows). Works fine
on a 300million row table. There is very high CPU usage during the run.
I've tried setting spark.dse.continuousPagingEnabled to false and I've
tried setting spark.
Thank you,
I should have mention hardware and software which I used in this experiment:
CPU: one Intel Xeon silver 4210 10 core 2.2G
Network: 1Gb
OS: Ubuntu 20.04.2 LTS
Java: 1.8.0_321 Oracle
Apache Cassandra 4.0.1
Data model is a single table:
text partitionKey, 15chars
int clust
Hi Everyone
We have migrated some of our clusters from Cassandra 3.11.11 to 4.0.1. We
do repairs periodically triggered by some automation. Each time we run
repair we do full `-full` sequential `-seq` primary `-pr` repairs for a
portion of the full ring range and we finish iterating over the full r