cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10422) Avoid anticompaction when doing subrange repair
Date Thu, 29 Oct 2015 17:03:27 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980807#comment-14980807
] 

Ariel Weisberg commented on CASSANDRA-10422:
--------------------------------------------

Looks like the 2.2 code merges to 3.0 and trunk without issue. Tests running now.
|[2.1 code|https://github.com/apache/cassandra/compare/apache:cassandra-2.1...aweisberg:CASSANDRA-10422-2.1?expand=1]|[utests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-10422-2.1-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-10422-2.1-dtest/]|
|[2.2 code|https://github.com/apache/cassandra/compare/apache:cassandra-2.2...aweisberg:CASSANDRA-10422-2.2?expand=1]|[utests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-10422-2.2-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-10422-2.2-dtest/]|

> Avoid anticompaction when doing subrange repair
> -----------------------------------------------
>
>                 Key: CASSANDRA-10422
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10422
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Ariel Weisberg
>             Fix For: 2.1.x, 2.2.x, 3.1
>
>
> If we do split the owned range in say 1000 parts, and then do one repair each, we could
potentially anticompact every sstable 1000 times (ie, we anticompact the repaired range out
1000 times). We should avoid anticompacting at all in these cases.



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

Mime
View raw message