On Sun, Jun 28, 2015 at 10:46 AM, Anuj Wadehra
wrote:
> Thanks Jake!! But I think most people have 2.0.x in Production right now
> as 2.1.6 is very recently declared Production Ready. I think the bug is too
> important to be left open in 2.0.x as it leads to data loss. Should I open
> JIRA?
>
So
Thanks Jake!! But I think most people have 2.0.x in Production right now as
2.1.6 is very recently declared Production Ready. I think the bug is too
important to be left open in 2.0.x as it leads to data loss. Should I open JIRA?
ThanksAnuj Wadehra
On Thursday, 25 June 2015 2:47 AM, Jake
This is no longer an issue in 2.1.
https://issues.apache.org/jira/browse/CASSANDRA-2434
We now make sure the replica we bootstrap from is the one that will no
longer own that range
On Wed, Jun 24, 2015 at 4:58 PM, Alain RODRIGUEZ wrote:
> It looks to me that can indeed happen theoretically (I m
It looks to me that can indeed happen theoretically (I might be wrong).
However,
- Hinted Handoff tends to remove this issue, if this is big worry, you
might want to make sure HH are enabled and well tuned
- Read Repairs (synchronous or not) might have mitigate things also, if you
read fresh data
Hi,
We faced a scenario where we lost little data after adding 2 nodes in the
cluster. There were intermittent dropped mutations in the cluster. Need to
verify my understanding how this may have happened to do Root Cause Analysis:
Scenario: 3 nodes, RF=3, Read / Write CL= Quorum
1. Due to o
