Re: Denormalization leads to terrible, rather than better, Cassandra performance -- I am really puzzled

Thank you both very much, Erick and Steve. Steve, 1. You are right on the target. I realized it later last week and did additional tests. I am in the process summarizing it and I am going to put it here as a comparison reference for others. 2. It is good to know. 3. Yes, I am using EBS. I under

Denormalization leads to terrible, rather than better, Cassandra performance -- I am really puzzled

Cassandra gurus, I am really puzzled by my observations,and hope to get some help explaining the results. Thanks in advance. I think it has always been advocated in Cassandracommunity that de-normalization leads to better performance. I wanted to seehow much performance improvement it can offer, bu

Re: CQL "Alter table" does not propagate to all nodes.

Thank you very much, Erick. Yes, we are using NTP. But your other suggestions and links are very helpful. I tried to grep MigrationStage from system.log and found "Can't send migration request: node /201.20.32.54 is down." around the time I ran the CQL, although that server is actually up running

CQL "Alter table" does not propagate to all nodes.

I have a 3-node cluster running Cassandra 2.0.6 on CentOS 6.5, with Jave 1.7.0_51. I ran a CQL statement like "alter table table_name with gc_grace_seconds=864000;" on node 1 in CQLSH, and it finished instantaneously. "desc keyspace" listed the table with the new value for gc_grace_seconds, and "

Re: CQL query throws TombstoneOverwhelmingException against a LeveledCompactionStrategy table

BTW, I am using Cassandra 2.0.6. Is this the same as CASSANDRA-6654 (Droppable tombstones are not being removed from LCS table despite being above 20%) ? I checked my table in JConsole and the droppable tombstone ratio of over 60%. If it is

CQL query throws TombstoneOverwhelmingException against a LeveledCompactionStrategy table

I have two tables. Table “event” stores data with SizeTieredCompactionStrategy, and table “event_index” acts as an index table with LeveledCompationStrategy, and with TimeUUID as its clustering column. For each record in event table, there will be 4 indices in the event_index table, and the overall