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
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 results in large amounts of compaction), how can this be possible?
I h
Hi,
right, QUORUM means that data is written to all replicas but the coordinator
waits for QUORUM responses before returning back to client. If a replica is out
of sync due to network or internal issue than consistency is ensured through:
- HintedHandoff (Automatically
http://www.datastax.com
