cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean Carlo <jean.jeancar...@gmail.com>
Subject Re: Do I have to use repair -inc with the option -par forcely?
Date Wed, 17 Feb 2016 19:57:26 GMT
Hi ,

Thx @alain for you reply. Yes we have the 2.1.12. We are  definitely
 facing CASSANDRA-10422
<https://issues.apache.org/jira/browse/CASSANDRA-10422>.
However I cannot run incremental repairs without add -par


@carlos if what you say it's correct, it will be really nice because the
process to migrate it's quite tedious if you have many nodes


Saludos

Jean Carlo

"The best way to predict the future is to invent it" Alan Kay

On Tue, Feb 16, 2016 at 4:39 PM, Carlos Rolo <rolo@pythian.com> wrote:

> +1 on what Alain said, but I do think if you are high enough on a 2.1.x
> (will look later) version you don't need to follow the documentation. It is
> outdated. Run a full repair, the you can start incremental repairs since
> the SSTables will have the metadata on them about the last repair.
>
>  Wait someone to confirm this/or confirm the docs are correct.
>
> Regards,
>
> Carlos Juzarte Rolo
> Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
>
> Pythian - Love your data
>
> rolo@pythian | Twitter: @cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo
> <http://linkedin.com/in/carlosjuzarterolo>*
> Mobile: +351 91 891 81 00 | Tel: +1 613 565 8696 x1649
> www.pythian.com
>
> On Tue, Feb 16, 2016 at 1:45 PM, Alain RODRIGUEZ <arodrime@gmail.com>
> wrote:
>
>> Hi,
>>
>> I am testing repairs repairs -inc -par and I can see that in all my nodes
>>> the numbers of sstables explode to 5k from 5 sstables.
>>
>>
>> This looks like a known issue, see
>> https://issues.apache.org/jira/browse/CASSANDRA-10422
>> Make sure your version is higher than 2.1.12, 2.2.4, 3.0.1, 3.1 to avoid
>> this (and you are indeed facing CASSANDRA-10422).
>> I am not sure you are facing this though, as you don't seem to be using
>> subranges (nodetool repair -st  and -et options)
>>
>> *It is anyway to run repairs incrementals but not -par ?*
>>>
>>> I know that is it not possible to run sequential repair with incremental
>>> repair at the same time.
>>>
>>
>>
>> From http://www.datastax.com/dev/blog/more-efficient-repairs
>> "Incremental repairs can be opted into via the -inc option to nodetool
>> repair. This is compatible with both sequential and parallel (-par)
>> repair, e.g., bin/nodetool -par -inc <ks> <cf>."
>> So you should be able to remove -par. Not sure this will solve your issue
>> though.
>>
>>
>> Did you respect this process to migrate to incremental repairs?
>>
>> https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/opsRepairNodesMigration.html#opsRepairNodesMigration__ol_dxj_gp5_2s
>>
>> C*heers,
>> -----------------
>> Alain Rodriguez
>> France
>>
>> The Last Pickle
>> http://www.thelastpickle.com
>>
>>
>>
>> 2016-02-10 17:45 GMT+01:00 Jean Carlo <jean.jeancarl48@gmail.com>:
>>
>>> Hi guys; The question is on the subject.
>>>
>>> I am testing repairs repairs -inc -par and I can see that in all my
>>> nodes the numbers of sstables explode to 5k from 5 sstables.
>>>
>>> I cannot permit this behaivor on my cluster in production.
>>>
>>> *It is anyway to run repairs incrementals but not -par ?*
>>>
>>> I know that is it not possible to run sequential repair with incremental
>>> repair at the same time.
>>>
>>> Best regards
>>>
>>> Jean Carlo
>>>
>>> "The best way to predict the future is to invent it" Alan Kay
>>>
>>
>>
>
> --
>
>
>
>

Mime
View raw message