cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: cassandra 0.6.1 read returns wrong data?
Date Mon, 02 Aug 2010 19:29:57 GMT
Yes, it is deterministic (but compaction could change which precise
keys are affected)

On Mon, Aug 2, 2010 at 1:15 PM, Jianing Hu <jianing@gmail.com> wrote:
> Does that bug cause *random* data read errors? Looks like it may fail
> in a deterministic way, but I'm not familiar with the code base so
> please correct me if I'm wrong.
>
> On Fri, Jul 30, 2010 at 8:49 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
>> This is probably a bug fixed in 0.6.2:
>>
>>  * fix size of row in spanned index entries (CASSANDRA-1056)
>>
>> You should upgrade to 0.6.4 (due out this weekend).
>>
>> On Wed, Jul 28, 2010 at 7:47 PM, Jianing Hu <jianing@gmail.com> wrote:
>>> We recently migrated part of our MySQL database to a 3-node Cassandra
>>> cluster with a replication factor of 3. Couple of days ago we noticed
>>> that Cassandra sometimes returns the wrong data. Not corrupted data,
>>> but data for a different key than the one being asked for. This error
>>> appears to be random and intermittent, and happens for maybe every 10K
>>> reads. I'm working on a test suite that can reproduce this. Meanwhile
>>> just wanted to ask if anyone has seen this problem before? I've tried
>>> consistency levels of both QUORUM and ONE, and see the issue with
>>> both.
>>>
>>> Thanks,
>>> - Jianing
>>>
>>
>>
>>
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of Riptano, the source for professional Cassandra support
>> http://riptano.com
>>
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com

Mime
View raw message