Anyone have anymore thoughts on this at all? Struggling to understand it..
> On 9 Jun 2017, at 11:32, Chris Stokesmore
> wrote:
>
> Hi Anuj,
>
> Thanks for the reply.
>
> 1). We are using Cassandra 2.2.8, and our repair commands we are comparing
> are
>
gt;
>
> Sent from Yahoo Mail on Android
> <https://overview.mail.yahoo.com/mobile/?.src=Android>
> On Tue, Jun 6, 2017 at 9:33 PM, Chris Stokesmore
> mailto:chris.elsm...@demandlogic.co>> wrote:
> Thank you for the excellent and clear description of the different ver
not repair entire
> data.
>
> 4. 885 ranges? From where did you get this number? Logs? Can you share the
> number ranges printed in logs for both inc and pr case?
>
>
> Thanks
> Anuj
>
>
> Sent from Yahoo Mail on Android
> <https://overview.mail.
t; Sent from Yahoo Mail on Android
> <https://overview.mail.yahoo.com/mobile/?.src=Android>
> On Tue, Jun 6, 2017 at 4:27 PM, Chris Stokesmore
> wrote:
> Hi all,
>
> Wondering if anyone had any thoughts on this? At the moment the long running
> repairs cause us to
Hi all,
Wondering if anyone had any thoughts on this? At the moment the long running
repairs cause us to be running them on two nodes at once for a bit of time,
which obivould increases the cluster load.
On 2017-05-25 16:18 (+0100), Chris Stokesmore wrote:
> Hi,>
>
> We are
Hi,
We are running a 7 node Cassandra 2.2.8 cluster, RF=3, and had been running
repairs with the —pr option, via a cron job that runs on each node once per
week.
We changed that as some advice on the Cassandra IRC channel said it would cause
more anticompaction and
http://docs.datastax.com/e
