cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10422) Avoid anticompaction when doing subrange repair
Date Tue, 10 Nov 2015 16:56:11 GMT


Marcus Eriksson commented on CASSANDRA-10422:

[~aweisberg] (sorry for not replying quicker) - isIncremental is for telling the other nodes
which sstables to use when doing the repair (for merkle tree calculation and streaming, if
isIncremental is true, we will only use the sstables that are not marked as repaired) - isGlobal
is used to tell the other nodes if we can actually do the anticompaction - if all nodes that
have the range are included in the repair.

> Avoid anticompaction when doing subrange repair
> -----------------------------------------------
>                 Key: CASSANDRA-10422
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Ariel Weisberg
>             Fix For: 3.1, 2.1.x, 2.2.x
> 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

View raw message