cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahdi Mohammadi (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11933) Improve Repair performance
Date Fri, 03 Jun 2016 01:13:59 GMT


Mahdi Mohammadi commented on CASSANDRA-11933:

CI Reports 5 test failures in dtest and testall together. Does that mean something is wrong
with my change?

> Improve Repair performance
> --------------------------
>                 Key: CASSANDRA-11933
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cyril Scetbon
>            Assignee: Mahdi Mohammadi
> During  a full repair on a ~ 60 nodes cluster, I've been able to see that this stage
can be significant (up to 60 percent of the whole time) :
> It's merely caused by the fact that
calls {code}ss.getLocalRanges(keyspaceName){code} everytime and that it takes more than 99%
of the time. This call takes 600ms when there is no load on the cluster and more if there
is. So for 10k ranges, you can imagine that it takes at least 1.5 hours just to compute ranges.

> Underneath it calls [ReplicationStrategy.getAddressRanges|]
which can get pretty inefficient ([~jbellis]'s [words|])
> *ss.getLocalRanges(keyspaceName)* should be cached to avoid having to spend hours on

This message was sent by Atlassian JIRA

View raw message