Or, write with LOCAL_QUORUM, and only do a repair if you're going to
replace a host (if one host fails, repair the surviving replicas before you
bootstrap the replacement), and let read repairs handle consistency. This
is only strictly safe because if all of your writes are TTL'd and you never
dele
Are you running with RF=3 and QUORUM on both read and write?
If so, I think as long as your fill job reports errors and retries you can
probably get away without repairing.
You can also hedge your bets by doing the data load with ALL, though of
course that has an availability tradeoff.
Personally,
Hi everyone,
There are a lot of articles, and, probably this question was asked already
many times, but I still not 100% sure.
We have a table, which we load almost full every night with spark job and
consistency LOCAL_QUORUM and record TTL 7 days. This is to remove some
records if they are not p
