Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
Date: Sat, 12 Apr 2014 03:38:27 +0400
Message-ID: 
 <CAGNEgBeCzV_E1xCGAeM2siY=tGg-C42Syk_DJqtjV5LHcweaPw@mail.gmail.com>
Subject: Eventual consistency with replication factor 1
From: Ravil Bayramgalin <brainopia@evilmartians.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a1134b004963d7e04f6ccd425

--001a1134b004963d7e04f6ccd425
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I've got classical eventual consistency symptoms (read after write returns
empty result) but there is a surprising twist. The keyspace has replication
factor 1 (it's used as a cache) so how can I get a stale result?

Cassandra version 1.2.15.

Consistency settings (although I think they should not matter with
one-replica case):
Read =E2=80=94 CL.ONE
Write =E2=80=94 CL.ALL

If you need any additional info I would be happy to provide!

--001a1134b004963d7e04f6ccd425
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ve got classical eventual consistency symptoms (read=
 after write returns empty result) but there is a surprising twist. The key=
space has replication factor 1 (it&#39;s used as a cache) so how can I get =
a stale result?<br>
<div><br></div><div>Cassandra version 1.2.15.</div><div><br></div><div>Cons=
istency settings (although I think they should not matter with one-replica =
case):</div><div>Read =E2=80=94 CL.ONE</div><div>Write =E2=80=94 CL.ALL</di=
v><div><br></div>
<div>If you need any additional info I would be happy to provide!</div></di=
v>

--001a1134b004963d7e04f6ccd425--