(ColumnFamilySerializer.java:144)
On Wed, Feb 6, 2013 at 11:32 AM, Terry Cumaranatunge wrote:
> I've gotten timeouts on clients when using Cassandra 1.1.8 in a cluster of
> 12 nodes, but I don't see the same behavior when using Cassandra 1.0.10.
> So, to do a controlled experiment, the followi
I've gotten timeouts on clients when using Cassandra 1.1.8 in a cluster of
12 nodes, but I don't see the same behavior when using Cassandra 1.0.10.
So, to do a controlled experiment, the following was tried:
1. Started with Cassandra 1.0.10. Built a database and ran our test tools
against it to bu
Hi,
We have a Cassandra 1.0 cluster that we run with RF=3 and perform
operations using a consistency level of quorum. We use batch_mutate for all
inserts and updates for atomicity across column families with the same row
key, but use the thrift interface remove API call in C++ to delete a row so
t
I have a cluster of 8 nodes all running 1.0. The stats shown on the 1st node
on one of the CFs for the number of keys is much larger than expected. The
first node shows the key count estimate to be 9.2M whereas the rest report
~650K on each node. The 650K is in the correct neighborhood of the numbe
Hello,
I'm seeng the following exception during compaction. This is happening on
Linux (RHEL 6) running Cassandra 1.0. This particular instance is with
Leveled compaction, but we have seen this error in the past with SizeTiered
compaction as well. We are not using compression.
Any ideas on what m
Hello,
If you set a ttl and expire a column, I've read that this eventually turns
into a tombstone and will be cleaned out by the GC. Are expirations
considered a form of delete that still requires a node repair to be run in
gc_grace_period seconds? The operations guide says you have to run node
r
