cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleksandr Shulgin <oleksandr.shul...@zalando.de>
Subject Re: To Repair or Not to Repair
Date Tue, 13 Aug 2019 16:14:18 GMT
On Thu, Mar 14, 2019 at 9:55 PM Jonathan Haddad <jon@jonhaddad.com> wrote:

> My coworker Alex (from The Last Pickle) wrote an in depth blog post on
> TWCS.  We recommend not running repair on tables that use TWCS.
>
> http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html
>

Hi,

I was wondering about this again, as I've noticed one of the nodes in our
cluster accumulating ten times the number of files compared to the average
across the rest of cluster.  The files are all coming from a table with
TWCS and repair (running with Reaper) is ongoing.  The sudden growth
started around 24 hours ago as the affected node was restarted due to
failing AWS EC2 System check.  Now I'm thinking again if we should be
running those repairs at all. ;-)

In the Summary of the blog post linked above, the following is written:

It is advised to disable read repair on TWCS tables, and use an agressive
tombstone purging strategy as digest mismatches during reads will still
trigger read repairs.


Was it meant to read "disable anti-entropy repair" instead?  I find it
confusing otherwise.

Regards,
--
Alex

Mime
View raw message