>>
>>The Reaper user mailing list is located here, for questions and feedback:
>>https://groups.google.com/forum/#!forum/tlp-apache-cassandra-reaper-users
>>
>>Thanks,
>>Jon
--
Dominik Petrovic
s configured and lose nodes you should replace the node with
>>one from the same rack. You then need to repair, and definitely don't
>>decommission until you do.
>>
>>Also 40 nodes with 256 vnodes is not a fun time for repair.
>>
>>On 15 Sep. 2017 03:36,
eff Jirsa <jji...@gmail.com>:
>
>With one datacenter/region, what did you discover in an outage you think
>you'll solve with network topology strategy? It should be equivalent for a
>single D.C.
>
>--
>Jeff Jirsa
>
>
>On Sep 14, 2017, at 8:47 AM, Dominik Petrov
pairs and the ALTER, which you MAY be able to
>work around if we know more about your cluster.
>
>How many nodes
>How many regions
>How many replicas per region when you're done?
>
>
>
>
>--
>Jeff Jirsa
>
>
>On Sep 13, 2017, at 2:04 PM, Dominik Petrovic
the steps for Cassandra 2.1 but the token
distribution in the ring didn't change so I'm assuming that wasn't the right
think to do.
I also perform a nodetool repair -pr but nothing changed as well.
Some advice?
--
Dominik Petrovic
