Hm that question is like "My car does not start - whats the problem?".
You have to monitor, monitor, monitor, monitor. I'd strongly advice to
graph as many metrics as you can. Read them from the JMX interface and
write them to a TSDB, visualize them e.g. with Grafana.
Then read logs, trace your que
Dear Cassandra Users,
I have some issues since few days with the following cluster:
- 5 nodes
- Cassandra 3.7
- 2 seed nodes
- 1 keyspace with RF=2, 300Go / nodes, WRITE_LEVEL=ONE, READ_LEVEL=ONE
- 1 enormous table (90% of the keyspace)
- TTL for each line insered
The cluster is write or
ing DseDelegateSnitch
>
> Thanks,
> SC
> From: aa...@thelastpickle.com
> Subject: Re: cluster issues
> Date: Tue, 29 Jan 2013 20:15:45 +1300
> To: user@cassandra.apache.org
>
> • We can always be proactive in keeping the time sync. But, Is there
> any way to recover from a
I am using DseDelegateSnitch
Thanks,SC
From: aa...@thelastpickle.com
Subject: Re: cluster issues
Date: Tue, 29 Jan 2013 20:15:45 +1300
To: user@cassandra.apache.org
We can always be proactive in keeping the time sync. But, Is there any way to
recover from a time drift (in a reactive manner
> We can always be proactive in keeping the time sync. But, Is there any way to
> recover from a time drift (in a reactive manner)? Since it was a lab
> environment, I dropped the KS (deleted data directory)
There is a way to remove future dated columns, but it not for the faint
hearted.
Basic
One of our node in a 3 node cluster drifted by ~ 20-25 seconds. While I figured
this pretty quickly, I had few questions that am looking for some answers.
We can always be proactive in keeping the time sync. But, Is there any way to
recover from a time drift (in a reactive manner)? Since it wa
