Yes it can cause issues.
No there's no way to disable it in any current release (I think it finally
landed to disable it in 4.0, but dont have the JIRA handy)
https://issues.apache.org/jira/browse/CASSANDRA-13418 was added to 3.11.1
and higher to let people consciously say "ignore overlaps from
the reason for this all test i conducted i we have a prod cluster of 2.1
where twcs was defined on many tables a few months ago (all tables with
read repair setting disabled, also speculative retry disabled), and looked
very good. a month ago we noticed most of the servers had their data all in
sounds like the foreground read repair can cause issues to twcs (mix old
and new data in same sstable), is there a way to disable the foreground
read repair? is that indeed the case that it's problematic?
On Mon, Dec 17, 2018 at 9:21 AM Gil Ganz wrote:
> hey jeff, attaching more information.
