If you want consistent reads you have to use the CL that enforces it. There’s no way around it. On Fri, Feb 9, 2018 at 2:35 PM Mahdi Ben Hamida <ma...@signalfx.com> wrote:
> In this case, we only write using CAS (code guarantees that). We also > never update, just insert if not exist. Once a hash exists, it never > changes (it may get deleted later and that'll be a CAS delete as well). > > -- > Mahdi. > > On 2/9/18 1:38 PM, Jeff Jirsa wrote: > > > > On Fri, Feb 9, 2018 at 1:33 PM, Mahdi Ben Hamida <ma...@signalfx.com> > wrote: > >> Under what circumstances would we be reading inconsistent results ? Is >> there a case where we end up reading a value that actually end up not being >> written ? >> >> >> > > If you ever write the same value with CAS and without CAS (different code > paths both updating the same value), you're using CAS wrong, and > inconsistencies can happen. > > > >
