Good catch. We ran repairs few times but don't do it on a regular basis.
But I found no dependency between count of DigestMismatchExceptions and
latency spikes (see attached graphs for example).
One important point I didn't mention in the original mail is that all
requests (both reads and writes) h
Latency and mismatch matches may not align but mismatch means data is not
in sync AND can cause read latency.
On Thu, Dec 13, 2018 at 2:34 AM Виталий Савкин
wrote:
> Good catch. We ran repairs few times but don't do it on a regular basis.
> But I found no dependency between count of DigestMismat
Providing logs or more technical information might be helpful. If it is
cassandra-lucene related issue, perhaps it'll be better to open a issue in
their github repo?
Dinesh
On Wednesday, December 12, 2018, 11:17:06 PM GMT+5:30, Brian Spindler
wrote:
Hi all, we recently started using
Hi all ,
My colleague opened Jira ticket for the issue but we are struggling with
this issue for a while and we have space issues :
https://issues.apache.org/jira/browse/CASSANDRA-14929
After removing a node from the cluster, a table that is defined as TWCS,
has sstables from different time win
Remove node will stream data from all windows to remote nodes , so some
compaction is expected
Would need to see the sstablemetadata to understand what’s happening there.
--
Jeff Jirsa
> On Dec 13, 2018, at 10:26 PM, Roy Burstein wrote:
>
> Hi all ,
> My colleague opened Jira ticket for t
