You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Sean Bridges <se...@globalrelay.net> on 2016/10/24 16:04:51 UTC
incremental repairs with -pr flag?
Hey,
In the datastax documentation on repair [1], it says,
"The partitioner range option is recommended for routine maintenance. Do
not use it to repair a downed node. Do not use with incremental repair
(default for Cassandra 3.0 and later)."
Why is it not recommended to use -pr with incremental repairs?
Thanks,
Sean
[1]
https://docs.datastax.com/en/cassandra/3.x/cassandra/operations/opsRepairNodesManualRepair.html
--
Sean Bridges
senior systems architect
Global Relay
_sean.bridges@globalrelay.net_ <ma...@globalrelay.net>
*866.484.6630 *
New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore
(+65.3158.1301)
Global Relay Archive supports email, instant messaging, BlackBerry,
Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter,
Facebook and more.
Ask about *_Global Relay Message_*
<http://www.globalrelay.com/services/message> - The Future of
Collaboration in the Financial Services World
All email sent to or from this address will be retained by Global
Relay's email archiving system. This message is intended only for the
use of the individual or entity to which it is addressed, and may
contain information that is privileged, confidential, and exempt from
disclosure under applicable law. Global Relay will not be liable for any
compliance or technical information provided herein. All trademarks are
the property of their respective owners.
Re: incremental repairs with -pr flag?
Posted by Bruno Lavoie <bl...@brunol.com>.
Another point, I've done another test on my 5 node cluster.
Created a keyspace with replication factor of 5 and inserted some data in
it.
Run a full repair on each node to make sstable appear on disk.
Then run multiple times on each nodes:
1 - nodetool repair
2 - nodetool repair -pr
Due to incremental repair, if I altenate between these 2 commands, no files
change on disk... It means anti-compaction is used.
But on the wall-clock timing, the first method takes an average of 15
seconds and the second one an average of 10 seconds.
But there's no mutation between these commands...
Bruno
On Fri, Jan 13, 2017 at 3:43 PM, Bruno Lavoie <bl...@brunol.com> wrote:
> Thanks for your reply,
>
> But can't figure out why it's not recommendend, by DataStax, to run
> primary-range with incremental repair...
>
> It's just doing less work on each repair call on the repaired node.
> At the end, when all the nodes are repaired using either method, all data
> is equally consistent? (excluding read/writes occuring during repair)
>
> Does it harm something?
> Maybe I'm missing something... or to want to understand too much.
>
> I've run a test on a node with the 2 ways, and the output is pretty
> similar (5 nodes, replication factor 2):
> «nodetool repair» https://gist.github.com/blavoie/
> cc6bbad10ec1b0bf403b3486765d1e0b
> «nodetool repair -pr» https://gist.github.com/blavoie/
> f9c5aaf6bf75ad7d2e6b40213cbf6021
>
> On the same topic: when is it advised to do a full repair?
> https://docs.datastax.com/en/cassandra/3.0/cassandra/
> operations/opsRepairNodesWhen.html
>
> They recommend running incremental daily, and full-repairs weekly or
> monthly.
> And a full repair eliminate anti-compaction, is it bad?
> Does it generates a lot of files to run regularly anti-compaction stuff?
>
> Thanks again
> Bruno Lavoie
>
> On Wed, Jan 11, 2017 at 3:23 PM, Paulo Motta <pa...@gmail.com>
> wrote:
>
>> The objective of non-incremental primary-range repair is to avoid redoing
>> work, but with incremental repair anticompaction will segregate repaired
>> data so no extra work is done on the next repair.
>>
>> You should run nodetool repair [ks] [table] in all nodes sequentially.
>> The more often you run, the smaller time repair will take, so just choose
>> the periodicity that suits you better provided it's below gc_grace_seconds.
>>
>>
>> 2017-01-10 13:40 GMT-02:00 Bruno Lavoie <bl...@brunol.com>:
>>
>>>
>>>
>>> On 2016-10-24 13:39 (-0500), Alexander Dejanovski <
>>> alex@thelastpickle.com> wrote:
>>> > Hi Sean,
>>> >
>>> > In order to mitigate its impact, anticompaction is not fully executed
>>> when
>>> > incremental repair is run with -pr. What you'll observe is that running
>>> > repair on all nodes with -pr will leave sstables marked as unrepaired
>>> on
>>> > all of them.
>>> >
>>> > Then, if you think about it you realize it's no big deal as -pr is
>>> useless
>>> > with incremental repair : data is repaired only once with incremental
>>> > repair, which is what -pr intended to fix on full repair, by repairing
>>> all
>>> > token ranges only once instead of times the replication factor.
>>> >
>>> > Cheers,
>>> >
>>> > Le lun. 24 oct. 2016 18:05, Sean Bridges <se...@globalrelay.net>
>>> a
>>> > écrit :
>>> >
>>> > > Hey,
>>> > >
>>> > > In the datastax documentation on repair [1], it says,
>>> > >
>>> > > "The partitioner range option is recommended for routine
>>> maintenance. Do
>>> > > not use it to repair a downed node. Do not use with incremental
>>> repair
>>> > > (default for Cassandra 3.0 and later)."
>>> > >
>>> > > Why is it not recommended to use -pr with incremental repairs?
>>> > >
>>> > > Thanks,
>>> > >
>>> > > Sean
>>> > >
>>> > > [1]
>>> > > https://docs.datastax.com/en/cassandra/3.x/cassandra/operati
>>> ons/opsRepairNodesManualRepair.html
>>> > > --
>>> > >
>>> > > Sean Bridges
>>> > >
>>> > > senior systems architect
>>> > > Global Relay
>>> > >
>>> > > *sean.bridges@globalrelay.net* <se...@globalrelay.net>
>>> > >
>>> > > *866.484.6630 *
>>> > > New York | Chicago | Vancouver | London (+44.0800.032.9829) |
>>> Singapore
>>> > > (+65.3158.1301)
>>> > >
>>> > > Global Relay Archive supports email, instant messaging, BlackBerry,
>>> > > Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter,
>>> > > Facebook and more.
>>> > >
>>> > > Ask about *Global Relay Message*
>>> > > <http://www.globalrelay.com/services/message> - The Future of
>>> > > Collaboration in the Financial Services World
>>> > >
>>> > > All email sent to or from this address will be retained by Global
>>> Relay's
>>> > > email archiving system. This message is intended only for the use of
>>> the
>>> > > individual or entity to which it is addressed, and may contain
>>> information
>>> > > that is privileged, confidential, and exempt from disclosure under
>>> > > applicable law. Global Relay will not be liable for any compliance or
>>> > > technical information provided herein. All trademarks are the
>>> property of
>>> > > their respective owners.
>>> > >
>>> > > --
>>> > -----------------
>>> > Alexander Dejanovski
>>> > France
>>> > @alexanderdeja
>>> >
>>> > Consultant
>>> > Apache Cassandra Consulting
>>> > http://www.thelastpickle.com
>>> >
>>>
>>> Hello,
>>>
>>> Was looking for exactly the same detail about the Datastax
>>> documentation, and not sure to understand everything from your response. I
>>> looked at my Cassandra: The Definitive Guide and nothing about this detail
>>> too.
>>>
>>> IIRC:
>>> - with incremental repair, it's safe to simply run 'nodetool repair' on
>>> each node, without any overhead or wasted resources (merkle trees building,
>>> compaction, etc)?
>>> - I've read that we must manually run manual anti-entropy repair on each
>>> node weekly or before the gc_grace_seconds (default 10 days)? Or only on
>>> returning dead node ?
>>>
>>> What's bad about running incremental repair on primary ranges only, node
>>> by node? Looks like a stepwise method to keep data consistent..
>>>
>>> In many sources I'm looking at, all examples are as «nodetool repair
>>> -pr» and no metion about using -full with -pr like here:
>>> http://www.datastax.com/dev/blog/repair-in-cassandra
>>>
>>>
>>> So, to keep a system healthy, with less impact:
>>> - what command to run nighly?
>>> - what command to run weekly?
>>>
>>> We're using C* 3.x
>>>
>>> Thanks
>>> Bruno Lavoie
>>>
>>>
>>
>
Re: incremental repairs with -pr flag?
Posted by Bruno Lavoie <bl...@brunol.com>.
Thanks for your reply,
But can't figure out why it's not recommendend, by DataStax, to run
primary-range with incremental repair...
It's just doing less work on each repair call on the repaired node.
At the end, when all the nodes are repaired using either method, all data
is equally consistent? (excluding read/writes occuring during repair)
Does it harm something?
Maybe I'm missing something... or to want to understand too much.
I've run a test on a node with the 2 ways, and the output is pretty similar
(5 nodes, replication factor 2):
«nodetool repair»
https://gist.github.com/blavoie/cc6bbad10ec1b0bf403b3486765d1e0b
«nodetool repair -pr»
https://gist.github.com/blavoie/f9c5aaf6bf75ad7d2e6b40213cbf6021
On the same topic: when is it advised to do a full repair?
https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsRepairNodesWhen.html
They recommend running incremental daily, and full-repairs weekly or
monthly.
And a full repair eliminate anti-compaction, is it bad?
Does it generates a lot of files to run regularly anti-compaction stuff?
Thanks again
Bruno Lavoie
On Wed, Jan 11, 2017 at 3:23 PM, Paulo Motta <pa...@gmail.com>
wrote:
> The objective of non-incremental primary-range repair is to avoid redoing
> work, but with incremental repair anticompaction will segregate repaired
> data so no extra work is done on the next repair.
>
> You should run nodetool repair [ks] [table] in all nodes sequentially. The
> more often you run, the smaller time repair will take, so just choose the
> periodicity that suits you better provided it's below gc_grace_seconds.
>
>
> 2017-01-10 13:40 GMT-02:00 Bruno Lavoie <bl...@brunol.com>:
>
>>
>>
>> On 2016-10-24 13:39 (-0500), Alexander Dejanovski <al...@thelastpickle.com>
>> wrote:
>> > Hi Sean,
>> >
>> > In order to mitigate its impact, anticompaction is not fully executed
>> when
>> > incremental repair is run with -pr. What you'll observe is that running
>> > repair on all nodes with -pr will leave sstables marked as unrepaired on
>> > all of them.
>> >
>> > Then, if you think about it you realize it's no big deal as -pr is
>> useless
>> > with incremental repair : data is repaired only once with incremental
>> > repair, which is what -pr intended to fix on full repair, by repairing
>> all
>> > token ranges only once instead of times the replication factor.
>> >
>> > Cheers,
>> >
>> > Le lun. 24 oct. 2016 18:05, Sean Bridges <se...@globalrelay.net>
>> a
>> > écrit :
>> >
>> > > Hey,
>> > >
>> > > In the datastax documentation on repair [1], it says,
>> > >
>> > > "The partitioner range option is recommended for routine maintenance.
>> Do
>> > > not use it to repair a downed node. Do not use with incremental repair
>> > > (default for Cassandra 3.0 and later)."
>> > >
>> > > Why is it not recommended to use -pr with incremental repairs?
>> > >
>> > > Thanks,
>> > >
>> > > Sean
>> > >
>> > > [1]
>> > > https://docs.datastax.com/en/cassandra/3.x/cassandra/operati
>> ons/opsRepairNodesManualRepair.html
>> > > --
>> > >
>> > > Sean Bridges
>> > >
>> > > senior systems architect
>> > > Global Relay
>> > >
>> > > *sean.bridges@globalrelay.net* <se...@globalrelay.net>
>> > >
>> > > *866.484.6630 *
>> > > New York | Chicago | Vancouver | London (+44.0800.032.9829) |
>> Singapore
>> > > (+65.3158.1301)
>> > >
>> > > Global Relay Archive supports email, instant messaging, BlackBerry,
>> > > Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter,
>> > > Facebook and more.
>> > >
>> > > Ask about *Global Relay Message*
>> > > <http://www.globalrelay.com/services/message> - The Future of
>> > > Collaboration in the Financial Services World
>> > >
>> > > All email sent to or from this address will be retained by Global
>> Relay's
>> > > email archiving system. This message is intended only for the use of
>> the
>> > > individual or entity to which it is addressed, and may contain
>> information
>> > > that is privileged, confidential, and exempt from disclosure under
>> > > applicable law. Global Relay will not be liable for any compliance or
>> > > technical information provided herein. All trademarks are the
>> property of
>> > > their respective owners.
>> > >
>> > > --
>> > -----------------
>> > Alexander Dejanovski
>> > France
>> > @alexanderdeja
>> >
>> > Consultant
>> > Apache Cassandra Consulting
>> > http://www.thelastpickle.com
>> >
>>
>> Hello,
>>
>> Was looking for exactly the same detail about the Datastax documentation,
>> and not sure to understand everything from your response. I looked at my
>> Cassandra: The Definitive Guide and nothing about this detail too.
>>
>> IIRC:
>> - with incremental repair, it's safe to simply run 'nodetool repair' on
>> each node, without any overhead or wasted resources (merkle trees building,
>> compaction, etc)?
>> - I've read that we must manually run manual anti-entropy repair on each
>> node weekly or before the gc_grace_seconds (default 10 days)? Or only on
>> returning dead node ?
>>
>> What's bad about running incremental repair on primary ranges only, node
>> by node? Looks like a stepwise method to keep data consistent..
>>
>> In many sources I'm looking at, all examples are as «nodetool repair -pr»
>> and no metion about using -full with -pr like here:
>> http://www.datastax.com/dev/blog/repair-in-cassandra
>>
>>
>> So, to keep a system healthy, with less impact:
>> - what command to run nighly?
>> - what command to run weekly?
>>
>> We're using C* 3.x
>>
>> Thanks
>> Bruno Lavoie
>>
>>
>
Re: incremental repairs with -pr flag?
Posted by Paulo Motta <pa...@gmail.com>.
The objective of non-incremental primary-range repair is to avoid redoing
work, but with incremental repair anticompaction will segregate repaired
data so no extra work is done on the next repair.
You should run nodetool repair [ks] [table] in all nodes sequentially. The
more often you run, the smaller time repair will take, so just choose the
periodicity that suits you better provided it's below gc_grace_seconds.
2017-01-10 13:40 GMT-02:00 Bruno Lavoie <bl...@brunol.com>:
>
>
> On 2016-10-24 13:39 (-0500), Alexander Dejanovski <al...@thelastpickle.com>
> wrote:
> > Hi Sean,
> >
> > In order to mitigate its impact, anticompaction is not fully executed
> when
> > incremental repair is run with -pr. What you'll observe is that running
> > repair on all nodes with -pr will leave sstables marked as unrepaired on
> > all of them.
> >
> > Then, if you think about it you realize it's no big deal as -pr is
> useless
> > with incremental repair : data is repaired only once with incremental
> > repair, which is what -pr intended to fix on full repair, by repairing
> all
> > token ranges only once instead of times the replication factor.
> >
> > Cheers,
> >
> > Le lun. 24 oct. 2016 18:05, Sean Bridges <se...@globalrelay.net>
> a
> > écrit :
> >
> > > Hey,
> > >
> > > In the datastax documentation on repair [1], it says,
> > >
> > > "The partitioner range option is recommended for routine maintenance.
> Do
> > > not use it to repair a downed node. Do not use with incremental repair
> > > (default for Cassandra 3.0 and later)."
> > >
> > > Why is it not recommended to use -pr with incremental repairs?
> > >
> > > Thanks,
> > >
> > > Sean
> > >
> > > [1]
> > > https://docs.datastax.com/en/cassandra/3.x/cassandra/operations/
> opsRepairNodesManualRepair.html
> > > --
> > >
> > > Sean Bridges
> > >
> > > senior systems architect
> > > Global Relay
> > >
> > > *sean.bridges@globalrelay.net* <se...@globalrelay.net>
> > >
> > > *866.484.6630 *
> > > New York | Chicago | Vancouver | London (+44.0800.032.9829) |
> Singapore
> > > (+65.3158.1301)
> > >
> > > Global Relay Archive supports email, instant messaging, BlackBerry,
> > > Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter,
> > > Facebook and more.
> > >
> > > Ask about *Global Relay Message*
> > > <http://www.globalrelay.com/services/message> - The Future of
> > > Collaboration in the Financial Services World
> > >
> > > All email sent to or from this address will be retained by Global
> Relay's
> > > email archiving system. This message is intended only for the use of
> the
> > > individual or entity to which it is addressed, and may contain
> information
> > > that is privileged, confidential, and exempt from disclosure under
> > > applicable law. Global Relay will not be liable for any compliance or
> > > technical information provided herein. All trademarks are the property
> of
> > > their respective owners.
> > >
> > > --
> > -----------------
> > Alexander Dejanovski
> > France
> > @alexanderdeja
> >
> > Consultant
> > Apache Cassandra Consulting
> > http://www.thelastpickle.com
> >
>
> Hello,
>
> Was looking for exactly the same detail about the Datastax documentation,
> and not sure to understand everything from your response. I looked at my
> Cassandra: The Definitive Guide and nothing about this detail too.
>
> IIRC:
> - with incremental repair, it's safe to simply run 'nodetool repair' on
> each node, without any overhead or wasted resources (merkle trees building,
> compaction, etc)?
> - I've read that we must manually run manual anti-entropy repair on each
> node weekly or before the gc_grace_seconds (default 10 days)? Or only on
> returning dead node ?
>
> What's bad about running incremental repair on primary ranges only, node
> by node? Looks like a stepwise method to keep data consistent..
>
> In many sources I'm looking at, all examples are as «nodetool repair -pr»
> and no metion about using -full with -pr like here:
> http://www.datastax.com/dev/blog/repair-in-cassandra
>
>
> So, to keep a system healthy, with less impact:
> - what command to run nighly?
> - what command to run weekly?
>
> We're using C* 3.x
>
> Thanks
> Bruno Lavoie
>
>
Re: incremental repairs with -pr flag?
Posted by Bruno Lavoie <bl...@brunol.com>.
On 2016-10-24 13:39 (-0500), Alexander Dejanovski <al...@thelastpickle.com> wrote:
> Hi Sean,
>
> In order to mitigate its impact, anticompaction is not fully executed when
> incremental repair is run with -pr. What you'll observe is that running
> repair on all nodes with -pr will leave sstables marked as unrepaired on
> all of them.
>
> Then, if you think about it you realize it's no big deal as -pr is useless
> with incremental repair : data is repaired only once with incremental
> repair, which is what -pr intended to fix on full repair, by repairing all
> token ranges only once instead of times the replication factor.
>
> Cheers,
>
> Le lun. 24 oct. 2016 18:05, Sean Bridges <se...@globalrelay.net> a
> écrit :
>
> > Hey,
> >
> > In the datastax documentation on repair [1], it says,
> >
> > "The partitioner range option is recommended for routine maintenance. Do
> > not use it to repair a downed node. Do not use with incremental repair
> > (default for Cassandra 3.0 and later)."
> >
> > Why is it not recommended to use -pr with incremental repairs?
> >
> > Thanks,
> >
> > Sean
> >
> > [1]
> > https://docs.datastax.com/en/cassandra/3.x/cassandra/operations/opsRepairNodesManualRepair.html
> > --
> >
> > Sean Bridges
> >
> > senior systems architect
> > Global Relay
> >
> > *sean.bridges@globalrelay.net* <se...@globalrelay.net>
> >
> > *866.484.6630 *
> > New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore
> > (+65.3158.1301)
> >
> > Global Relay Archive supports email, instant messaging, BlackBerry,
> > Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter,
> > Facebook and more.
> >
> > Ask about *Global Relay Message*
> > <http://www.globalrelay.com/services/message> - The Future of
> > Collaboration in the Financial Services World
> >
> > All email sent to or from this address will be retained by Global Relay's
> > email archiving system. This message is intended only for the use of the
> > individual or entity to which it is addressed, and may contain information
> > that is privileged, confidential, and exempt from disclosure under
> > applicable law. Global Relay will not be liable for any compliance or
> > technical information provided herein. All trademarks are the property of
> > their respective owners.
> >
> > --
> -----------------
> Alexander Dejanovski
> France
> @alexanderdeja
>
> Consultant
> Apache Cassandra Consulting
> http://www.thelastpickle.com
>
Hello,
Was looking for exactly the same detail about the Datastax documentation, and not sure to understand everything from your response. I looked at my Cassandra: The Definitive Guide and nothing about this detail too.
IIRC:
- with incremental repair, it's safe to simply run 'nodetool repair' on each node, without any overhead or wasted resources (merkle trees building, compaction, etc)?
- I've read that we must manually run manual anti-entropy repair on each node weekly or before the gc_grace_seconds (default 10 days)? Or only on returning dead node ?
What's bad about running incremental repair on primary ranges only, node by node? Looks like a stepwise method to keep data consistent..
In many sources I'm looking at, all examples are as «nodetool repair -pr» and no metion about using -full with -pr like here:
http://www.datastax.com/dev/blog/repair-in-cassandra
So, to keep a system healthy, with less impact:
- what command to run nighly?
- what command to run weekly?
We're using C* 3.x
Thanks
Bruno Lavoie
RE: incremental repairs with -pr flag?
Posted by Sean Bridges <Se...@globalrelay.net>.
Thanks.
Sean
________________________________
From: Alexander Dejanovski [alex@thelastpickle.com]
Sent: Monday, October 24, 2016 10:39 AM
To: user@cassandra.apache.org
Subject: Re: incremental repairs with -pr flag?
Hi Sean,
In order to mitigate its impact, anticompaction is not fully executed when incremental repair is run with -pr. What you'll observe is that running repair on all nodes with -pr will leave sstables marked as unrepaired on all of them.
Then, if you think about it you realize it's no big deal as -pr is useless with incremental repair : data is repaired only once with incremental repair, which is what -pr intended to fix on full repair, by repairing all token ranges only once instead of times the replication factor.
Cheers,
Le lun. 24 oct. 2016 18:05, Sean Bridges <se...@globalrelay.net>> a écrit :
Hey,
In the datastax documentation on repair [1], it says,
"The partitioner range option is recommended for routine maintenance. Do not use it to repair a downed node. Do not use with incremental repair (default for Cassandra 3.0 and later)."
Why is it not recommended to use -pr with incremental repairs?
Thanks,
Sean
[1] https://docs.datastax.com/en/cassandra/3.x/cassandra/operations/opsRepairNodesManualRepair.html
--
Sean Bridges
senior systems architect
Global Relay
sean.bridges@globalrelay.net <ma...@globalrelay.net>
866.484.6630
New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore (+65.3158.1301)
Global Relay Archive supports email, instant messaging, BlackBerry, Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, Facebook and more.
Ask about Global Relay Message<http://www.globalrelay.com/services/message> - The Future of Collaboration in the Financial Services World
All email sent to or from this address will be retained by Global Relay's email archiving system. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Global Relay will not be liable for any compliance or technical information provided herein. All trademarks are the property of their respective owners.
--
-----------------
Alexander Dejanovski
France
@alexanderdeja
Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com<http://www.thelastpickle.com/>
Re: incremental repairs with -pr flag?
Posted by Alexander Dejanovski <al...@thelastpickle.com>.
Hi Sean,
In order to mitigate its impact, anticompaction is not fully executed when
incremental repair is run with -pr. What you'll observe is that running
repair on all nodes with -pr will leave sstables marked as unrepaired on
all of them.
Then, if you think about it you realize it's no big deal as -pr is useless
with incremental repair : data is repaired only once with incremental
repair, which is what -pr intended to fix on full repair, by repairing all
token ranges only once instead of times the replication factor.
Cheers,
Le lun. 24 oct. 2016 18:05, Sean Bridges <se...@globalrelay.net> a
écrit :
> Hey,
>
> In the datastax documentation on repair [1], it says,
>
> "The partitioner range option is recommended for routine maintenance. Do
> not use it to repair a downed node. Do not use with incremental repair
> (default for Cassandra 3.0 and later)."
>
> Why is it not recommended to use -pr with incremental repairs?
>
> Thanks,
>
> Sean
>
> [1]
> https://docs.datastax.com/en/cassandra/3.x/cassandra/operations/opsRepairNodesManualRepair.html
> --
>
> Sean Bridges
>
> senior systems architect
> Global Relay
>
> *sean.bridges@globalrelay.net* <se...@globalrelay.net>
>
> *866.484.6630 *
> New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore
> (+65.3158.1301)
>
> Global Relay Archive supports email, instant messaging, BlackBerry,
> Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter,
> Facebook and more.
>
> Ask about *Global Relay Message*
> <http://www.globalrelay.com/services/message> - The Future of
> Collaboration in the Financial Services World
>
> All email sent to or from this address will be retained by Global Relay's
> email archiving system. This message is intended only for the use of the
> individual or entity to which it is addressed, and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. Global Relay will not be liable for any compliance or
> technical information provided herein. All trademarks are the property of
> their respective owners.
>
> --
-----------------
Alexander Dejanovski
France
@alexanderdeja
Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com