2018, 8:42 PM Igor Zubchenok wrote:
> According docs at
> http://cassandra.apache.org/doc/latest/operating/repair.html?highlight=single
>
>
> *The -pr flag will only repair the “primary” ranges on a node, so you can
> repair your entire cluster by running nodetool repair -p
According docs at
http://cassandra.apache.org/doc/latest/operating/repair.html?highlight=single
*The -pr flag will only repair the “primary” ranges on a node, so you can
repair your entire cluster by running nodetool repair -pr on each node in
a single datacenter.*
But I saw many places, where
I want to repair all nodes at all data centers.
Example:
DC1
nodeA
nodeB
nodeC
DC2
node D
node E
node F
If I run `nodetool repair -pr` at nodeA nodeB and nodeC, will all ranges be
repaired?
On Fri, 8 Jun 2018 at 17:57 Rahul Singh
wrote:
> From DS dox : "Do not use -pr with thi
>From DS dox : "Do not use -pr with this option to repair only a local data
>center."
On Jun 8, 2018, 10:42 AM -0400, user@cassandra.apache.org, wrote:
>
> nodetool repair -pr
Hi!
I want to repair all nodes in all datacenters.
Should I run *nodetool repair -pr* at all nodes of a SINGLE datacenter or
at all nodes of ALL datacenters?
--
Regards,
Igor Zubchenok
CTO at Multi Brains LLC
Founder of taxistartup.com saytaxi.com chauffy.com
Skype: igor.zubchenok
ne node at a time or three at once?
>>
>> On Wed, Feb 21, 2018 at 10:20 AM, Fd Habash wrote:
>>
>>> We have had a 15 node cluster across three zones and cluster repairs
>>> using ‘nodetool repair -pr’ took about 3 hours to finish. Lately, we shrunk
>>&
4
>
> 07:41:4295% 3.00 73.46
> 14530.76 29521 4
>
> 07:41:4298% 4.00182.79
> 25109.16 61214 4
>
> 07:41:4299% 4.00 182.79
Thank you
From: Fd Habash
Sent: Thursday, February 22, 2018 9:00 AM
To: user@cassandra.apache.org
Subject: RE: Cluster Repairs 'nodetool repair -pr' Cause Severe IncreaseinRead
Latency After Shrinking Cluster
“ data was allowed to fully rebalance/repair/drain before the nex
4
Thank you
From: Carl Mueller
Sent: Wednesday, February 21, 2018 4:33 PM
To: user@cassandra.apache.org
Subject: Re: Cluster Repairs 'nodetool repair -pr' Cause Severe Increase inRead
Latency After Shrinking Cluster
Hm nodetool decommision performs the stream
right?
>>> You removed one node at a time or three at once?
>>>
>>> On Wed, Feb 21, 2018 at 10:20 AM, Fd Habash wrote:
>>>
>>>> We have had a 15 node cluster across three zones and cluster repairs
>>>> using ‘nodetool repair -pr’ took a
t; wrote:
>
>> What is your replication factor?
>> Single datacenter, three availability zones, is that right?
>> You removed one node at a time or three at once?
>>
>> On Wed, Feb 21, 2018 at 10:20 AM, Fd Habash wrote:
>>
>>> We have had a 15 node clu
1, 2018 at 10:20 AM, Fd Habash wrote:
>
>> We have had a 15 node cluster across three zones and cluster repairs
>> using ‘nodetool repair -pr’ took about 3 hours to finish. Lately, we shrunk
>> the cluster to 12. Since then, same repair job has taken up to 12 hours to
>&g
te:
>
>> We have had a 15 node cluster across three zones and cluster repairs
>> using ‘nodetool repair -pr’ took about 3 hours to finish. Lately, we shrunk
>> the cluster to 12. Since then, same repair job has taken up to 12 hours to
>> finish and most times, it never does
irs using
> ‘nodetool repair -pr’ took about 3 hours to finish. Lately, we shrunk the
> cluster to 12. Since then, same repair job has taken up to 12 hours to finish
> and most times, it never does.
>
> More importantly, at some point during the repair cycle, we see read
&g
What is your replication factor?
Single datacenter, three availability zones, is that right?
You removed one node at a time or three at once?
On Wed, Feb 21, 2018 at 10:20 AM, Fd Habash wrote:
> We have had a 15 node cluster across three zones and cluster repairs using
> ‘nodetool repa
We have had a 15 node cluster across three zones and cluster repairs using
‘nodetool repair -pr’ took about 3 hours to finish. Lately, we shrunk the
cluster to 12. Since then, same repair job has taken up to 12 hours to finish
and most times, it never does.
More importantly, at some point
.
On September 28, 2017 at 11:46:47 AM, Dmitry Buzolin (dbuz5ga...@gmail.com)
wrote:
Hi All,
Can someone confirm if
"nodetool repair -pr -j2" does run with -inc too? I see the docs mention -inc
is set by default, but I am not sure if it is enabled when -pr option is used
Hi All,
Can someone confirm if
"nodetool repair -pr -j2" does run with -inc too? I see the docs mention -inc
is set by default, but I am not sure if it is enabled when -pr option is used.
Thanks!
-
To unsubscribe, e-
Hi. After I've run token-ranged repair from node at 12.5.13.125 with
nodetool repair -full -st ${start_tokens[i]} -et ${end_tokens[i]}
on every token range, I got this node load:
-- Address Load Tokens Owns Rack
UN 12.5.13.141 23.94 GB 256 32.3% rack1
DN 12.5.13.125
Thank you for all the replies. It has been enlightening to read. I think I
now have a better idea of repair, ranges, replicas and how the data is
distributed. It also seems that using -pr would be the best way to go in my
scenario with 1.x+
Thank you for all the feedback. Glad to see such an acti
der. You must not use,
> disclose, distribute, copy, print or rely on this e-mail. If you have
> received this message in error, please contact the sender immediately and
> irrevocably delete this message and any copies.
>
> From: Sylvain Lebresne [mailto:sylv...@datastax.com]
>
ylv...@datastax.com]
Sent: Tuesday, June 05, 2012 11:02
To: user@cassandra.apache.org
Subject: Re: nodetool repair -pr enough in this scenario?
On Tue, Jun 5, 2012 at 8:44 AM, Viktor Jevdokimov
mailto:viktor.jevdoki...@adform.com>> wrote:
Understand simple mechanics first, decide how to act l
mains the property of the sender. You must not use,
> disclose, distribute, copy, print or rely on this e-mail. If you have
> received this message in error, please contact the sender immediately and
> irrevocably delete this message and any copies.
>
> *From:* David D
ly and
> irrevocably delete this message and any copies.
>
> *From:* David Daeschler [mailto:david.daesch...@gmail.com]
> *Sent:* Tuesday, June 05, 2012 08:59
> *To:* user@cassandra.apache.org
> *Subject:* nodetool repair -pr enough in this scenario?
>
> ** **
>
>
opies.
From: David Daeschler [mailto:david.daesch...@gmail.com]
Sent: Tuesday, June 05, 2012 08:59
To: user@cassandra.apache.org
Subject: nodetool repair -pr enough in this scenario?
Hello,
Currently I have a 4 node cassandra cluster on CentOS64. I have been running
nodetool repair (no -pr option) on a
Hello,
Currently I have a 4 node cassandra cluster on CentOS64. I have been
running nodetool repair (no -pr option) on a weekly schedule like:
Host1: Tue, Host2: Wed, Host3: Thu, Host4: Fri
In this scenario, if I were to add the -pr option, would this still be
sufficient to prevent forgotten del
26 matches
Mail list logo
