Abhishek,
can you file an issue on our github repo so that we can further discuss
this ? https://github.com/thelastpickle/cassandra-reaper/issues
Thanks,
On Wed, Oct 19, 2016 at 1:20 PM Abhishek Aggarwal <
abhishek.aggarwa...@snapdeal.com> wrote:
> Hi Alex,
>
> that i already did and it worked
Hi Alex,
that i already did and it worked but my question is if the passed value of
incremental repair flag is different from the existing value then it
should allow to create new repair_unit instead of getting repair_unit based
on cluster name/ keyspace /column combination.
and also if i
Hi Abhishek,
This shows you have two repair units for the same keyspace/table with
different incremental repair settings.
Can you delete your prior repair run (the one with incremental repair set
to false) and then create the new one with incremental repair set to true ?
Let me know how that
is there a way to start the incremental repair using the reaper. we
completed full repair successfully and after that i tried to run the
incremental run but getting the below error.
A repair run already exist for the same cluster/keyspace/table but with a
different incremental repair
