cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10768) Optimize the way we check if a token is repaired in anticompaction
Date Wed, 02 Dec 2015 09:30:11 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Eriksson updated CASSANDRA-10768:
----------------------------------------
    Component/s: Streaming and Messaging
                 Compaction

> Optimize the way we check if a token is repaired in anticompaction
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-10768
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10768
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction, Streaming and Messaging
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.12, 2.2.4, 3.0.1, 3.1
>
>
> When we anticompact we check each token if it is within a repaired range, this is very
inefficient with many tokens as we do a linear search instead of sorting the ranges and doing
a binary search (or even just keeping track of the next right-boundary and checking against
that to avoid 2 comparisons)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message