Re: unnecessary tombstone's transmission during repair process

Gus, we've found the cause. It was a problem in Cassandra, but it has been already fixed in cassandra 1.1.6. Commit with the problem: 2c69e2ea757be9492a095aa22b5d51234c4b4102 You can see it at https://issues.apache.org/jira/secure/attachment/12544204/CASSANDRA-4561-CS.patch Commit with the fix:

Re: Cassandra nodes loaded unequally

Hi Ben, I suggest you to compare amount of queries for each node. May be the problem is on the client side. Yoy can do that using JMX: "org.apache.cassandra.db:type=ColumnFamilies,keyspace=,columnfamily=","ReadCount" "org.apache.cassandra.db:type=ColumnFamilies,keyspace=,columnfamily=","WriteCount

Re: unnecessary tombstone's transmission during repair process

Sylvain, I've seen to the code. Yes, you right about local deletion time. But it contradicts to the tests results. Do you have any thoughts how to explain result of the second test after patch applying? Our patch: diff --git a/src/java/org/apache/cassandra/db/DeletedColumn.java b/src/java/org/

unnecessary tombstone's transmission during repair process

Hi Guys, I have a question about merkle tree construction and repair process. When mercle tree is constructing it calculates hashes. For DeletedColumn it calculates hash using value. Value of DeletedColumn is a serialized local deletion time. We know that local deletion time can be different on di

cassandra 1.2 beta in production

Hi Guys, What known critical bugs are there that couldn't allow to use 1.2 beta 1 in production? We don't use cql and secondary indexes. -- Best regards** Zotov Alexey Grid Dynamics Skype: azotcsit