It gets complicated when you have RF > 1, because a subrange can involve
multiple nodes, and a node can't run multiple repairs concurrently for
the same table. Multiple DCs also complicates things, as the
describering command doesn't separate the token ranges by DC. In my
opinion, it's best to use Cassandra reaper.
On 23/03/2021 05:25, Surbhi Gupta wrote:
Does describering not give the correct sub ranges for each node ?
On Mon, 22 Mar 2021 at 20:28, manish khandelwal
<[email protected] <mailto:[email protected]>>
wrote:
Also try to use Cassandra reaper (as Kane also mentioned) for
subrange repair. Doing subrange repair yourself may lead to a lot
of trouble as calculating correct subranges is not an easy task.
On Tue, Mar 23, 2021 at 3:38 AM Kane Wilson <[email protected]> wrote:
-pr on all nodes takes much longer as you'll do at least
triple the amount of merkle calculations I believe (with RF 3)
and tends to be quite problematic.
Subrange is the way to go, which is what cassandra-reaper will
do for you if you have it set up.
raft.so <https://raft.so> - Cassandra consulting, support, and
managed services
On Tue, Mar 23, 2021 at 7:33 AM Surbhi Gupta
<[email protected] <mailto:[email protected]>>
wrote:
Hi,
We are on open source 3.11.5 .
We need to repair a production cluster .
We are using num_token as 256 .
What will be a better option to run repair ?
1. nodetool -pr (Primary range repair on all nodes, one
node at a time)
OR
2. nodetool -st -et (Subrange repair , taking the ranges
for each node from nodetool describering) and run 256
repairs on each node .
Thanks
Surbhi
