Ticket created at https://issues.apache.org/jira/browse/CASSANDRA-11933
Thanks
> On May 31, 2016, at 13:54, Paulo Motta wrote:
>
> Good catch! It definitely makes sense to cache this call for a single
> repair job as it calls ReplicationStrategy.getAddressRanges underneath
> which can get pretty
Good catch! It definitely makes sense to cache this call for a single
repair job as it calls ReplicationStrategy.getAddressRanges underneath
which can get pretty inefficient (
https://github.com/apache/cassandra/blob/3dcbe90e02440e6ee534f643c7603d50ca08482b/src/java/org/apache/cassandra/locator/Abs
Hi C* developers,
Digging in the code because of a time issue during a repair full on our ~ 60
nodes cluster, I've been able to see that this stage can be significant (up to
60 percent of) :
https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/service/StorageSer
