cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arya Goudarzi <gouda...@gmail.com>
Subject Re: 1.1.5 Missing Insert! Strange Problem
Date Thu, 27 Sep 2012 21:49:27 GMT
I was restarting Cassandra nodes again today. 1 hour later my support team
let me know that a customer has reported some missing data. I suppose this
is the same issue. The application logs show that our client got success
from the Thrift log and proceeded with responding to the user and I could
grep the commit log for a missing record like I did before.

We have durable writes enabled. To me, it seams like when stuff are in
memtables and hasn't been flushed to disk, when I restart the node, the
commit log doesn't get replayed correctly.

Please advice.

On Thu, Sep 27, 2012 at 2:43 PM, Arya Goudarzi <goudarzi@gmail.com> wrote:

> Thanks for your reply. I did grep on the commit logs for the offending key
> and grep showed Binary file matches. I am trying to use this tool to
> extract the commitlog and actually confirm if the mutation was a write:
>
> https://github.com/carloscm/cassandra-commitlog-extract.git
>
>
> On Thu, Sep 27, 2012 at 1:45 AM, Sylvain Lebresne <sylvain@datastax.com>wrote:
>
>> > I can verify the existence of the key that was inserted in Commitlogs
>> of both replicas however it seams that this record was never inserted.
>>
>> Out of curiosity, how can you verify that?
>>
>> --
>> Sylvain
>>
>
>

Mime
View raw message