It sounds like the commitlog has been replayed however I have really no
idea whether this could have happened. Anyone?
2012/4/13 Alain RODRIGUEZ
> The commitlog_total_space_in_mb was not set, I set it to avoid having the
> same problem in the future.
>
> I am aware of the over-counting problem i
The commitlog_total_space_in_mb was not set, I set it to avoid having the
same problem in the future.
I am aware of the over-counting problem introduced by the counters. The
point is that I use them to make statistics per hours. I can understand
having some wrong counts in the column corresponding
> However after recovering from this issue (freeing some space and fixing the
> value of "commitlog_total_space_in_mb" in cassandra.yaml)
Did the commit log grow larger than commitlog_total_space_in_mb ?
> I realized that all statistics were all destroyed. I have bad values on every
> single c
By the way, I am using Cassandra 1.0.7, CL = ONE (R/W), RF = 2, 2 EC2
c1.medium nodes cluster
Alain
2012/4/10 Alain RODRIGUEZ
> Hi, I'm experimenting a strange and very annoying phenomena.
>
> I had a problem with the commit log size which grew too much and full one
> of the hard disks in all m
Hi, I'm experimenting a strange and very annoying phenomena.
I had a problem with the commit log size which grew too much and full one
of the hard disks in all my nodes almost at the same time (2 nodes only,
RF=2, so the 2 nodes are behaving exactly in the same way)
My data are mounted in an othe