If you notice an increase in the amount of data that Cassandra stores in
SSTables, or if you receive error messages about failed compactions, check the time of
the last successful compaction for selected SSTables.
Unsuccessful compaction might cause the disk that Cassandra uses to run out of free
- In the nodetool utility, run the
- In the
compacted_at column, verify the last time a successful
compaction was performed for the SSTables that experience an increase in data
size, or are the subject of error messages.
- If the amount of time that elapsed from the last successful compaction for the
selected SSTables is significantly higher than for other SSTables, investigate
the source of the problem, for example, by performing other Cassandra
For more information, see the Troubleshooting section of the
Apache Cassandra documentation.