Hi Anuj.
I don't think this decision depends on you scenario, but on your write
consistency level instead.
Maintenance repair is an anti-entropy operation intended to make all nodes
consistent.
Think of the situation where, with one DC, one of your nodes is down (or
being replaced) for a while (
Hi,
Can someone take this?
ThanksAnuj
On Mon, 8 Feb, 2016 at 11:44 pm, Anuj Wadehra wrote:
Hi,
Setup:
We are on 2.0.14. We have some deployments with just one DC(RF:3) while others
with two DCs (RF:3,RF:3).
We ALWAYS use LOCAL_QUORUM for both Reads and Writes.
Scenario:
---
Hi,
Setup:
We are on 2.0.14. We have some deployments with just one DC(RF:3) while others
with two DCs (RF:3,RF:3).
We ALWAYS use LOCAL_QUORUM for both Reads and Writes.
Scenario:
-
We used to run nodetool repair on all tables every gc_grace_seconds. Recently,
we decided to id
