Re: problem starting incremental repair using TheLastPicke Reaper

[Alexander Dejanovski]

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 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 delete the repair_unit then due to referential constraints i
> need to delete repair_segment and repair_run as well which will delete the
> run history corresponds to the repaid_unit.
>
> Abhishek Aggarwal
>
> *Senior Software Engineer*
> *M*: +91 8861212073 <+91%2088612%2012073> , 8588840304
> *T*: 0124 6600600 *EXT*: 12128
> ASF Center -A, ASF Center Udyog Vihar Phase IV,
> Download Our App
> [image: A]
> 
>  [image:
> A]
> 
>  [image:
> W]
> 
>
> On Wed, Oct 19, 2016 at 4:44 PM, Alexander Dejanovski <
> a...@thelastpickle.com> wrote:
>
> 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 works,
>
>
> On Wed, Oct 19, 2016 at 10:45 AM Abhishek Aggarwal <
> abhishek.aggarwa...@snapdeal.com> wrote:
>
>
> 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 value.Requested value: true | Existing value:
> false
>
>
> --
> -
> Alexander Dejanovski
> France
> @alexanderdeja
>
> Consultant
> Apache Cassandra Consulting
> http://www.thelastpickle.com
>
>
> --
-
Alexander Dejanovski
France
@alexanderdeja

Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: problem starting incremental repair using TheLastPicke Reaper

[Abhishek Aggarwal]

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 delete the repair_unit then due to referential constraints i
need to delete repair_segment and repair_run as well which will delete the
run history corresponds to the repaid_unit.

Abhishek Aggarwal

*Senior Software Engineer*
*M*: +91 8861212073 , 8588840304
*T*: 0124 6600600 *EXT*: 12128
ASF Center -A, ASF Center Udyog Vihar Phase IV,
Download Our App
[image: A]

[image:
A]

[image:
W]


On Wed, Oct 19, 2016 at 4:44 PM, Alexander Dejanovski <
a...@thelastpickle.com> wrote:

> 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 works,
>
>
> On Wed, Oct 19, 2016 at 10:45 AM Abhishek Aggarwal <
> abhishek.aggarwa...@snapdeal.com> wrote:
>
>>
>> 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 value.Requested value: true | Existing value:
>> false
>>
>>
>> --
> -
> Alexander Dejanovski
> France
> @alexanderdeja
>
> Consultant
> Apache Cassandra Consulting
> http://www.thelastpickle.com
>

Re: problem starting incremental repair using TheLastPicke Reaper

[Alexander Dejanovski]

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 works,


On Wed, Oct 19, 2016 at 10:45 AM Abhishek Aggarwal <
abhishek.aggarwa...@snapdeal.com> wrote:

>
> 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 value.Requested value: true | Existing value:
> false
>
>
> --
-
Alexander Dejanovski
France
@alexanderdeja

Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

problem starting incremental repair using TheLastPicke Reaper

[Abhishek Aggarwal]

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 value.Requested value: true | Existing value:
false