cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Roth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13226) StreamPlan for incremental repairs flushing memtables unnecessarily
Date Tue, 28 Feb 2017 09:29:45 GMT

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

Benjamin Roth commented on CASSANDRA-13226:
-------------------------------------------

Isn't this also true for non-incremental repairs?
Merkle tree calculation also triggers a flush and any repair begins with a merkle tree. So
there is no need to flush as the inconsistent dataset to be streamed for repair is always
contained in SSTables flushed by MT calculation before.

> StreamPlan for incremental repairs flushing memtables unnecessarily
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-13226
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13226
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Blake Eggleston
>            Assignee: Blake Eggleston
>            Priority: Minor
>             Fix For: 4.0
>
>
> Since incremental repairs are run against a fixed dataset, there's no need to flush memtables
when streaming for them.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message