Thanks for the tip. Checked nodetool ring on all nodes and they all have a
consistent view of the ring. We have had other problems like nodes crashing
etc so anything could have happened, but we're sure we didnt issue a nodetool
move command.
From: Tyler Hobbs [mailto:ty...@datastax.com]
We have a 10 node cluster (v0.7.9) split into 2 datacenters. Three times we
have seen nodes move themselves to different locations in the ring. In each
case, the move unbalanced the ring. In one case a node moved to the opposite
side of the ring.
Sometime after the first spontaneous move we
No, these were not wide rows. They are rows that formerly had one or 2
columns. The columns are deleted but the empty rows dont go away, even after
gc_grace_secs.
So if I understand... the empty row will only be removed after gc_grace if
enough compactions have occurred so that all the column
This is an old thread from December 27, 2011. I interpret the yes answer to
mean you do not have to explicitly delete an empty row after all of its columns
have been deleted, the empty row (i.e. row key) will automatically be deleted
eventually (after gc_grace). Is that true? I am not
Hello,
I'm trying to access a Cassandra 0.7 cluster in a hadoop map-reduce job (hadoop
0.20.2) and seeing a thrift library conflict. Hadoop uses an older version of
thrift than hector 0.7, and this older version is getting picked up by my job,
causing the following exception:
FATAL
