In any case: Monitoring disk-space is very very important.
So, why doesn't cassandra monitor it itself and stop accepting writes if it
runs out of space?
For one thing, it's non-trivial to do accurately because disk space
usage varies over time due to background compaction and/or
And the data could be more evenly balanced, obviously. However the nodes
fails to startup because due of lacking disk space (instead of starting up
and denies further writes it appears to try to process the [6.6G!] commit
logs). So, I cannot perform any actions on it no more like
, very full.
Answer:
$ time cassandra -f
INFO 16:30:09,486 Heap size: 2143158272/2143158272
log4j:ERROR Failed to flush writer,
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java
On Dec 22, 2010, at 16:20, Peter Schuller wrote:
In any case: Monitoring disk-space is very very important.
So, why doesn't cassandra monitor it itself and stop accepting writes if it
runs out of space?
