We have configured Cassandra to run on a separate D drive but noticed that during compaction, it also uses a lot of space of our C partition, where we have the OS and DataMiner. Because the C partition has less space, we wonder about any action to prevent this situation...
During compaction, there should not be extra writes to drive C, unless Cassandra needs memory and Windows starts using a page file.
If correctly configured to have Cassandra on an separate drive D, drive C should only be used for:
- Commit logs (where Cassandra temporarily saves new data)
- Hint files (used for synchronization with other Cassandra nodes, such as on a Failover system)
Both of these are unrelated to compaction.