Understand simple mechanics first, decide how to act later.
Without -PR there's no difference from which host to run repair, it runs for
the whole 100% range, from start to end, the whole cluster, all nodes, at once.
With -PR it runs only for a primary range of a node you are running a repair.
In your case -pr would be just fine (see Viktor's explanation).
2012/6/5 Viktor Jevdokimov viktor.jevdoki...@adform.com
Understand simple mechanics first, decide how to act later.
** **
Without –PR there’s no difference from which host to run repair, it runs
for the whole 100% range,
On Tue, Jun 5, 2012 at 8:44 AM, Viktor Jevdokimov
viktor.jevdoki...@adform.com wrote:
Understand simple mechanics first, decide how to act later.
** **
Without –PR there’s no difference from which host to run repair, it runs
for the whole 100% range, from start to end, the whole
@cassandra.apache.org
Subject: Re: nodetool repair -pr enough in this scenario?
On Tue, Jun 5, 2012 at 8:44 AM, Viktor Jevdokimov
viktor.jevdoki...@adform.commailto:viktor.jevdoki...@adform.com wrote:
Understand simple mechanics first, decide how to act later.
Without -PR there's no difference from which host
and
irrevocably delete this message and any copies.
From: Sylvain Lebresne [mailto:sylv...@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
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
