Hi all,
Sorry, I tested with an old index jar. The cassandra-3.0.3 and
dsc-cassandra-3.0.3 packages are the same. The error happens in both, i
think we have fixed it and it will be included in next release (maybe
3.0.5.1).
1.- Full repair is very intensive, thats why your cluster is non responsive
during repair. You can try several ways to avoid this:
A.- Run nodetool repair -pr in every node one at a time. You'll divide
the repair in three slots.
B.- Maybe your use case fits in incremental repairs
Cheers
Eduardo Alonso
Vía de las dos Castillas, 33, Ática 4, 3ª Planta
28224 Pozuelo de Alarcón, Madrid
Tel: +34 91 828 6473 // www.stratio.com // *@stratiobd
<https://twitter.com/StratioBD>*
2016-05-09 8:34 GMT+02:00 Siddharth Verma <verma.siddha...@snapdeal.com>:
> Hi Eduardo,
> Thanks for your help on stratio index problem
>
> As per your questions.
>
> 1. We ran nodetool repair on one box(no range repair), but due to it,
> entire DC was non responsive.
> It was up, but we were not able to connect.
>
> 2. RF is 3, and we have 2 DCs each with 3 nodes.
>
> 3. Consistency level for writes is Local_Quorum.
>
> Thanks
> Siddharth Verma
>
