incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: Quorum read after quorum write guarantee
Date Thu, 14 Mar 2013 05:19:24 GMT
>> If you are doing reads and writes using QUOURM double check that your code is correct.
If it is provide some more info on what you are seeing. 
> 
> It seems correct. What more info could be of value?
Can you reproduce the fault in a small script/program?
We have a pretty solid history of Quourm / Quourm operations exhibiting strong consistency,
so if there is a problem we'll need a way to reproduce it. 

Cheers

-----------------
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 12/03/2013, at 2:31 AM, André Cruz <andre.cruz@co.sapo.pt> wrote:

> On Mar 12, 2013, at 6:04 AM, aaron morton <aaron@thelastpickle.com> wrote:
> 
>>> by a multiget will not find the just inserted data.
>> Can you explain how the data is not found. 
>> Does it not find new columns or does it return stale columns ? 
> 
> It does not find new columns, I don't overwrite data.
> 
>> If the read is run again does it return the expected value? 
> 
> Yes, when I go and check manually after this happens, the data is already there. However,
I think I saw an instance when the multiget query was executed twice in quick succession,
the first time it returned all the results, the second time it didn't. This only happened
once, so I filed it under X-Files.
> 
>> if you are getting stale data double check the the nodes / clients have their clocks
synchronised. 
> 
> That's a good tip, I'll check.
> 
>> If you are doing reads and writes using QUOURM double check that your code is correct.
If it is provide some more info on what you are seeing. 
> 
> It seems correct. What more info could be of value?
> 
> Thanks,
> André
> 


Mime
View raw message