[
https://issues.apache.org/jira/browse/CASSANDRA-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938617#comment-15938617
]
Paulo Motta commented on CASSANDRA-13226:
-----------------------------------------
I think the idea behind flushing on stream was to send the most up-to-date data
during bootstrap/rebuild/decommission/replace, but this doesn't apply to repair
since you will end up overstreaming non-validated data as pointed out by
[~brstgt]. In any case this minor improvement is subject to another ticket
since this ticket is already closed.
> 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)
