Hello all,
I had 2 of my systems upgraded to 3.0 from the same previous version.
The first cluster seem to be fine.
But the second, each node starts and then fails.
On the log I have the following on all of them:
INFO [main] 2015-11-27 19:40:21,168 ColumnFamilyStore.java:381 -
Initializing sy
There is a window after a node goes down that changes that node should have
gotten will be kept. If the node is down LONGER than that, it will server
stale data. If the consistency is greater than two, its data will be
ignored (if consistency one, its data could be the first returned, if
consistenc
Thanks!
Hadmut
Hello!
We have some strange troubles with cassandra startup. Cluster consists of 4
nodes. 32 Gb RAM per node, each node has about 30Gb of data, 8 CPU.
root@vega010:~# nodetool version ReleaseVersion: 2.2.1
So, before stop (using disablethrift, drain):
nodetool tpstats: Read Stage 0 0 3093579 0