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:
r 12, 2012 1:33 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: unnecessary tombstone's transmission during repair process
iff --git a/src/java/org/apache/cassandra/db/DeletedColumn.java
b/src/java/org/apache
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/
> 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.
The deletion time time is not local to each replica, it'
On Thu, Oct 11, 2012 at 8:41 AM, Alexey Zotov wrote:
> Value of DeletedColumn is a serialized local
> deletion time. We know that local deletion time can be different on
> different nodes for the same tombstone. So hashes of the same tombstone on
> different nodes will be different. Is it true?
Y
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
