Sure I can fill in the ticket. Here is what I have noticed so far, the count
of HH is not going up, which is good. I think what must have happened is
that after I restarted the cluster, no new hints were added just the old
one's are still around and not cleaned up, is that possible? Cannot say for
Could you put together some information on this in a ticket and references this
one https://issues.apache.org/jira/browse/CASSANDRA-3071
The short term fix is to disable HH. You will still get consistent reads.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
ht
So I have looked at the cluster from
- Cassandra-client - describe cluster => shows correctly - 3 nodes
- used the StorageService - JMX bean =>UnreachableNodes - shows 0
If all these show the correct ring state, why are hints being maintained,
looks like that is the only way to find out ab
So, I restarted the cluster (not rolling), but it is still maintaining hints
for the IP's that are no longer part of the ring. nodetool ring shows things
correctly (as only 3 nodes).
When I check thru the jmx hintedhandoff manager, it shows it is maintaining
the hints for those non existent IP's. S
Yup, you can check the what HH is doing via JMX.
there is a bug in 0.7 that can result in log files not been deleted
https://issues.apache.org/jira/browse/CASSANDRA-2829
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 22/08/2011
We have a lot of space on /data, and looks like it was flushing data fine
from file timestamps.
We did have a bit of goofup with IP's when bringing up a down node (and the
commit files have been around since then). Wonder if that is what triggered
it and we have a bunch of hinted handoff's being b
> When does the actual commit-data file get deleted.
>
> The flush interval on all my memtables is 60 minutes
They *should* be getting deleted when they no longer contain any data
that has not been flushed to disk. Are flushes definitely still
happening? Is it possible flushing has started failing
So no it did not fill in a minute, but ton's of header files were written in
a minute (is that normal, I assume these are marker files which get written
when memtables are flushed. The actual data files have been around for the
last 24 hours?
Somehow this all seems connected to "reintroduce node" e
Hi,
7.4, 3 node cluster, RF=3
Load has not changed much, on 2 of the 3 nodes the commit log filled up in
less than a minute (did not give a chance to recover). Now have been running
this cluster for abt 2-3 months without any problem. At this point I do not
see any unusual load (continue to inves
