Quite a few, see here: http://pastebin.com/SMnprHdp. In total about 3,000
ranges across the 3 nodes.
This is with vnodes disabled. It was at least an order of magnitude worse
when we had it enabled.
Flavien
On 20 January 2015 at 22:22, Robert Coli wrote:
> On Mon, Jan 19, 2015 at 5:44 PM, Flav
On Mon, Jan 19, 2015 at 5:44 PM, Flavien Charlon
wrote:
> Thanks Andi. The reason I was asking is that even though my nodes have
> been 100% available and no write has been rejected, when running an
> incremental repair, the logs still indicate that some ranges are out of
> sync (which then resul
-
> *From:* Flavien Charlon [flavien.char...@gmail.com]
> *Sent:* 19 January 2015 22:50
> *To:* user@cassandra.apache.org
> *Subject:* How do replica become out of sync
>
> Hi,
>
> When writing to Cassandra using CL = Quorum (or anything less than ALL),
> is it co
/ops_repair_nodes_c.html)
Regards
Andi
From: Flavien Charlon [flavien.char...@gmail.com]
Sent: 19 January 2015 22:50
To: user@cassandra.apache.org
Subject: How do replica become out of sync
Hi,
When writing to Cassandra using CL = Quorum (or anything less than ALL), is it
Hi,
When writing to Cassandra using CL = Quorum (or anything less than ALL), is
it correct to say that Cassandra tries to write to all the replica, but
only waits for Quorum?
If so, what can cause some replica to become out of sync when they're all
online?
Thanks
Flavien
