Cassandra doesn't guarantee writes make it to all replicas unless you use a
sufficiently high consistency level or run nodetool repair
What consistency level did you use for writes?
Have you run repair?
--
Jeff Jirsa
> On Aug 2, 2017, at 6:27 AM, Peng Xiao <2535...@qq.com> wrote:
>
> Hi the
Hi there,
We have a three DCs Cluster (two DCs with RF=3,one remote DC with RF=1),we
currently find that in DC1/DC2 select count(*) from t=1250,while in DC3 select
count(*) from t=750.
looks some data is missing in DC3(remote DC).there are no node down or anything
exceptional.
we only upgrade
You also need to set CommitLogSync to batch instead of periodic if you
Absolutely Cannot Lose Data.
On Mon, May 24, 2010 at 10:51 AM, Joe Stump wrote:
> This is largely FUD. Cassandra let's you choose how consistent you want
> writes to be. The more consistency you choose, the slower the writes,
Ryan King actually has a very nice, short and sweet explanation that cuts
through the FUD:
http://theryanking.com/entries/2010/04/29/potential-consistency/
On Mon, May 24, 2010 at 12:01 PM, Steve Lihn wrote:
> So if I set it up to be strongly consistent, I should have the same level
> of consis
On May 24, 2010, at 10:01 AM, Steve Lihn wrote:
> So if I set it up to be strongly consistent, I should have the same level of
> consistency as traditional relational DB ?
If you do, say, QUORUM on the consistency level it will ensure at least 2 out
of the 3 replicants have responded back that
So if I set it up to be strongly consistent, I should have the same level of
consistency as traditional relational DB ?
On the other hand, what will happen if I set it up as eventual consistent?
Will the data become inconsistent after a crash/reboot, similar to the case
of asynchronous replication
This is largely FUD. Cassandra let's you choose how consistent you want writes
to be. The more consistency you choose, the slower the writes, but it's very
unlikely with high consistency that you'll lose data.
That being said, if you write with a consistency level of 0 then, yes, you
could lose
I am evaluating Cassandra as a candidate for our next-gen database. One of
my colleagues told me that "it's not recommended to use it as your system of
Record because it CAN lose data". Can someone with architecture
understanding shed some light on under what circumstance Cassandra cluster
can eith
