For cqlengine we do quite a bit of write then read to ensure data was written correctly, across 1.2, 2.0, and 2.1. For what it's worth, I've never seen this issue come up. On a single node, Cassandra only acks the write after it's been written into the memtable. So, you'd expect to see the most recent data.
A possibility - if you're running in a VM, it's possible the clock isn't incrementing in real time? I've seen this happen with uuid1 generation - I was getting duplicates if I generated them fast enough. Perhaps you're writing 2 values one right after the other and they're getting the same millisecond precision timestamp. On Thu, Nov 6, 2014 at 10:26 AM, Robert Coli <rc...@eventbrite.com> wrote: > On Thu, Nov 6, 2014 at 6:14 AM, Brian Tarbox <briantar...@gmail.com> wrote: >> >> We write values to our keyspaces and then immediately read the values back >> (in our Cucumber tests). About 20% of the time we get the old value.....if >> we wait 1 second and redo the query (within the same java method) we get the >> new value. >> >> This is all happening on a single node...how is this possible? > > > It sounds unreasonable/unexpected to me, if you have a trivial repro case, I > would file a JIRA. > > =Rob > -- Jon Haddad http://www.rustyrazorblade.com twitter: rustyrazorblade
