Re: Quorum read after quorum write guarantee

2013-03-13 Thread aaron morton
>> 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 Qu

Re: Quorum read after quorum write guarantee

2013-03-12 Thread André Cruz
On Mar 12, 2013, at 6:04 AM, aaron morton 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 agai

Re: Quorum read after quorum write guarantee

2013-03-11 Thread aaron morton
> 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 ? If the read is run again does it return the expected value? if you are getting stale data double check the the nodes / clients have the

Re: Quorum read after quorum write guarantee

2013-03-11 Thread André Cruz
On Mar 11, 2013, at 5:02 PM, Tyler Hobbs wrote: > What kind of inserts and multiget queries are you running? I use the ColumnFamily objects. The pool is initialised with "write_consistency_level=ConsistencyLevel.QUORUM". The insert is a regular insert, so the QUORUM is used. When fetching I us

Re: Quorum read after quorum write guarantee

2013-03-11 Thread Tyler Hobbs
What kind of inserts and multiget queries are you running? On Sun, Mar 10, 2013 at 1:16 PM, André Cruz wrote: > On 10/03/2013, at 16:49, Chuan-Heng Hsiao > wrote: > > However, my guess is that cassandra only guarantee that > > if you successfully write and you successfully read, then quorum wi

Re: Quorum read after quorum write guarantee

2013-03-10 Thread André Cruz
On 10/03/2013, at 16:49, Chuan-Heng Hsiao wrote: > However, my guess is that cassandra only guarantee that > if you successfully write and you successfully read, then quorum will > give you the latest data. That's what I thought, but that's not what I'm seeing all the time. I have no errors read

Re: Quorum read after quorum write guarantee

2013-03-10 Thread André Cruz
Yes, same thread. Cassandra 1.1.5 btw. Sent from my iPhone On 10/03/2013, at 16:47, Dave Brosius wrote: > is the read and write happening on the same thread? > > On 03/10/2013 12:00 PM, André Cruz wrote: >> Hello. >> >> In my application it sometimes happens that I execute a multiget (I use

Re: Quorum read after quorum write guarantee

2013-03-10 Thread Chuan-Heng Hsiao
Hi André, I am just a user of cassandra and did not look into the code deeply. However, my guess is that cassandra only guarantee that if you successfully write and you successfully read, then quorum will give you the latest data. not finding the just inserted data may be due to the failure of s

Re: Quorum read after quorum write guarantee

2013-03-10 Thread Dave Brosius
is the read and write happening on the same thread? On 03/10/2013 12:00 PM, André Cruz wrote: Hello. In my application it sometimes happens that I execute a multiget (I use pycassa) to fetch data that I have just inserted. I use quorum writes and reads, and my RF is 3. I've noticed that some

Quorum read after quorum write guarantee

2013-03-10 Thread André Cruz
Hello. In my application it sometimes happens that I execute a multiget (I use pycassa) to fetch data that I have just inserted. I use quorum writes and reads, and my RF is 3. I've noticed that sometimes (1 in 1000 perhaps) an insert followed (300ms after) by a multiget will not find the just