This is a known issue until Cassandra 2.1
https://issues.apache.org/jira/browse/CASSANDRA-5202
-Tupshin
On Feb 6, 2014 10:05 PM, "Robert Coli" wrote:
> On Thu, Feb 6, 2014 at 8:39 AM, Ondřej Černoš wrote:
>
>> Update: I dropped the keyspace, the system keyspace, deleted all the data
>> and sta
On Thu, Feb 6, 2014 at 8:39 AM, Ondřej Černoš wrote:
> Update: I dropped the keyspace, the system keyspace, deleted all the data
> and started from fresh state. Now it behaves correctly. The previously
> reported state is therefore the result of the keyspace being dropped
> beforehand and recreat
Update: I dropped the keyspace, the system keyspace, deleted all the data
and started from fresh state. Now it behaves correctly. The previously
reported state is therefore the result of the keyspace being dropped
beforehand and recreated with no compression on sstables - maybe some
sstables were l
I ran nodetool scrub on nodes in the less corrupted datacenter and tried
nodetool rebuild from this datacenter.
This is the result:
2014-02-06 15:04:24.645+0100 [Thread-83] [ERROR] CassandraDaemon.java(191)
org.apache.cassandra.service.CassandraDaemon: Exception in thread
Thread[Thread-83,5,main]
Hi,
I am running a small 2 DC cluster of 3 nodes (each DC). I use 3 replicas in
both DCs (all 6 nodes have everything) on Cassandra 1.2.11. I populated the
cluster via cqlsh pipelined with a series of inserts. I use the cluster for
tests, the dataset is pretty small (hundreds of thousands of recor
