Re: Nodetool repair question

[Joel Knighton]

No - repair does not change token ownership. The up/down state of a node is
not related to token ownership.

On Tue, May 10, 2016 at 3:26 PM, Anubhav Kale 
wrote:

> Hello,
>
>
>
> Suppose I have 3 nodes, and stop Cassandra on one of them. Then I run a
> repair. Will repair move the token ranges from down node to other node ? In
> other words in any situation, does repair operation *ever* change token
> ownership ?
>
>
>
> Thanks !
>



-- 



Joel Knighton
Cassandra Developer | joel.knigh...@datastax.com


 

 

Nodetool repair question

[Anubhav Kale]

Hello,

Suppose I have 3 nodes, and stop Cassandra on one of them. Then I run a repair. 
Will repair move the token ranges from down node to other node ? In other words 
in any situation, does repair operation ever change token ownership ?

Thanks !

Cassandra nodetool repair question

[Andy Losey]

Afternoon, 

We are noticing nodetool repair processes are not completing after a weeks 
worth of time, and have resulted in some Cassandra nodes having more than one 
process running do to cron scheduled. We are also chasing some performance 
degradation after upgrading all nodes to version 1.2.8 last Friday and would 
like to resolve this multiple repairs running at once issue in an effort to 
troubleshoot our performance issues.

We'd like to know more about what is happening with the repair option. Is there 
a way to gracefully terminate them or any adverse affect to killing the 
processes we should look out for?

Thanks,
-- 
Andy L

Re: Cassandra nodetool repair question

[Andrey Ilinykh]

nodetool repair just triggers repair procedure. You can kill nodetool after
start, it doesn't change anything. To stop repair you have to use nodetool
stop VALIDATION|COMPACTION


Thank you,

  Andrey



On Thu, Aug 8, 2013 at 1:00 PM, Andy Losey and...@addthis.com wrote:

  Afternoon,

 We are noticing nodetool repair processes are not completing after a weeks
 worth of time, and have resulted in some Cassandra nodes having more than
 one process running do to cron scheduled. We are also chasing some
 performance degradation after upgrading all nodes to version 1.2.8 last
 Friday and would like to resolve this multiple repairs running at once
 issue in an effort to troubleshoot our performance issues.

 We'd like to know more about what is happening with the repair option. Is
 there a way to gracefully terminate them or any adverse affect to killing
 the processes we should look out for?

 Thanks,
 --
 Andy L

Re: Cassandra nodetool repair question

[Mohit Anchlia]

But node might be streaming data as well, in that case only option is to 
restart node that started streaming operation

Sent from my iPhone

On Aug 8, 2013, at 5:56 PM, Andrey Ilinykh ailin...@gmail.com wrote:

 nodetool repair just triggers repair procedure. You can kill nodetool after 
 start, it doesn't change anything. To stop repair you have to use nodetool 
 stop VALIDATION|COMPACTION
 
 
 Thank you,
 
   Andrey
 
 
 
 On Thu, Aug 8, 2013 at 1:00 PM, Andy Losey and...@addthis.com wrote:
 Afternoon,
 
 We are noticing nodetool repair processes are not completing after a weeks 
 worth of time, and have resulted in some Cassandra nodes having more than 
 one process running do to cron scheduled. We are also chasing some 
 performance degradation after upgrading all nodes to version 1.2.8 last 
 Friday and would like to resolve this multiple repairs running at once issue 
 in an effort to troubleshoot our performance issues.
 
 We'd like to know more about what is happening with the repair option. Is 
 there a way to gracefully terminate them or any adverse affect to killing 
 the processes we should look out for?
 
 Thanks,
 -- 
 Andy L
 

nodetool repair question

[Raj N]

Hi experts,
 Are there any benchmarks that quantify how long nodetool repair takes?
Something which says on this kind of hardware, with this much of data,
nodetool repair takes this long. The other question that I have is since
Cassandra recommends running nodetool repair within GCGracePeriodSeconds, is
it possible to introduce a setting in cassandra.yaml, that allows you to
specify the frequency of nodetool repair so that Cassandra can itself
determine when to run nodetool repair instead of setting up a cron job.
Since Cassandra knows about all its peers, it can be smart enough to also
decide which nodes can run repair concurrently. For example, if RF =3, and I
have 6 nodes, then 2 replicas which are responsible for different ranges in
the ring can run repair concurrently.

Thanks
-Raj

Re: nodetool repair question

[Edward Capriolo]

On Tue, Jul 5, 2011 at 1:27 PM, Raj N raj.cassan...@gmail.com wrote:

 Hi experts,
  Are there any benchmarks that quantify how long nodetool repair takes?
 Something which says on this kind of hardware, with this much of data,
 nodetool repair takes this long. The other question that I have is since
 Cassandra recommends running nodetool repair within GCGracePeriodSeconds, is
 it possible to introduce a setting in cassandra.yaml, that allows you to
 specify the frequency of nodetool repair so that Cassandra can itself
 determine when to run nodetool repair instead of setting up a cron job.
 Since Cassandra knows about all its peers, it can be smart enough to also
 decide which nodes can run repair concurrently. For example, if RF =3, and I
 have 6 nodes, then 2 replicas which are responsible for different ranges in
 the ring can run repair concurrently.

 Thanks
 -Raj


Currently Cassandra does not run repair automatically. You can use cron and
'nodetool repair' as a simple approach.

Re: nodetool repair question

[Raj N]

I know it doesn't. But is this a valid enhancement request?

On Tue, Jul 5, 2011 at 1:32 PM, Edward Capriolo edlinuxg...@gmail.comwrote:



 On Tue, Jul 5, 2011 at 1:27 PM, Raj N raj.cassan...@gmail.com wrote:

 Hi experts,
  Are there any benchmarks that quantify how long nodetool repair
 takes? Something which says on this kind of hardware, with this much of
 data, nodetool repair takes this long. The other question that I have is
 since Cassandra recommends running nodetool repair within
 GCGracePeriodSeconds, is it possible to introduce a setting in
 cassandra.yaml, that allows you to specify the frequency of nodetool repair
 so that Cassandra can itself determine when to run nodetool repair instead
 of setting up a cron job. Since Cassandra knows about all its peers, it can
 be smart enough to also decide which nodes can run repair concurrently. For
 example, if RF =3, and I have 6 nodes, then 2 replicas which are responsible
 for different ranges in the ring can run repair concurrently.

 Thanks
 -Raj


 Currently Cassandra does not run repair automatically. You can use cron and
 'nodetool repair' as a simple approach.