Column family has more SSTables than threshold but no minorcompaction is running

Column Family: CF_1 SSTable count: 249 Space used (live): 15120496328 Space used (total): 15120496328 Number of Keys (estimate): 18860800 Memtable Columns Count: 0 Memtable Data Size: 0

how to verify the row key is evenly distributed

Hi all, I have a CF using incremental integer as row keys. In a 5-node cluster with RandomPartitioner, I've noticed the rows are not assigned evenly across nodes--two of them are 5 times heavier loaded than the rest. In nodetool, I can do *getendpoints- Print the end points that owns the k

Re: create column family or keyspace returns null

That does the trick. Thanks. I should've read FAQ more thoroughly. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/create-column-family-or-keyspace-returns-null-tp6658215p6658464.html Sent from the cassandra-u...@incubator.apache.org mailing lis

Re: create column family or keyspace returns null

I restarted the cluster a couple of times. But the error message ERROR [HintedHandoff:4] 2011-08-05 16:42:30,893 AbstractCassandraDaemon.java (line 139) Fatal exception in thread Thread[HintedHandoff:4,1,main] keeps on coming back. And I still can't create any column family or keyspace. -- Vie

create column family or keyspace returns null

I got a 5-node cluster running on 0.8.2. From the system log I'm seeing the exact problem reported in https://issues.apache.org/jira/browse/CASSANDRA-2946. And any "create column family xyz" returns null. Is it related to CASSANDRA-2946? -- View this message in context: http://cassandra-user-i

Re: Read latency is over 1 minute on a column family with 400,000 rows

Thanks. I will upgrade to 0.8.1 then. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Read-latency-is-over-1-minute-on-a-column-family-with-400-000-rows-tp6639649p6642582.html Sent from the cassandra-u...@incubator.apache.org mailing list archive

Re: Read latency is over 1 minute on a column family with 400,000 rows

All compaction related settings in the yaml were untouched. The fingerprint column family has been populated three days ago and the cpu/disk usage were pretty low. I'd think Cassandra will silently start the compaction thread on my behalf and try to preserve the min/max thresholds, rather than wa

Re: Read latency is over 1 minute on a column family with 400,000 rows

It was set the min/4 max/32 Current compaction thresholds for MyKeyspace/Fingerprint: min = 4, max = 32 What could possibly cause cassandra to ignore these settings? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Read-latency-is-over-1-minute

Re: Read latency is over 1 minute on a column family with 400,000 rows

On the node that the compaction returned almost immediately: *woot@n50:~$ /opt/cassandra/bin/nodetool -h localhost compactionstats pending tasks: 66* However, messages shown on other nodes are: compaction type: Major keyspace: MyKeyspace column family: Fingerprint bytes compacted: 25505066421 byt

Re: Read latency is over 1 minute on a column family with 400,000 rows

Thanks. I did *./nodetool -h localhost compact keyspace columnfamily1 *. But it came back really quick and the cfstats doesn't seem change much. After compaction: Column Family: Fingerprint SSTable count: 2057 Space used (live): 164351343468

Re: Read latency is over 1 minute on a column family with 400,000 rows

If I do ./nodetool -h localhost compact keyspace columnfamily1 it will go out and compact coumnfamily1 on all the nodes not just the localhost, correct? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Read-latency-is-over-1-minute-on-a-column-fa

Read latency is over 1 minute on a column family with 400,000 rows

Hi, my read latency is really horrible and I can't figure out what went wrong. I'm running cassandra 0.8.0 on a 5 machine cluster. The Fingerprint ColumnFamily has 400,000 rows, each row has about 4,000 Super columns, and each super column has 1 to 4 columns. One row looks like: RowKey: 00c26f