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] [Commented] (CASSANDRA-13430) Cleanup isIncremental/repairedAt usage
Date Wed, 19 Apr 2017 08:48:41 GMT

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

Marcus Eriksson commented on CASSANDRA-13430:
---------------------------------------------

+1

> Cleanup isIncremental/repairedAt usage
> --------------------------------------
>
>                 Key: CASSANDRA-13430
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13430
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Blake Eggleston
>            Assignee: Blake Eggleston
>             Fix For: 4.0
>
>
> Post CASSANDRA-9143, there's no longer a reason to pass around {{isIncremental}} or {{repairedAt}}
in streaming sessions, as well as some places in repair. The {{pendingRepair}} & {{repairedAt}}
values should only be set at the beginning/finalize stages of incremental repair and just
follow sstables around as they're streamed. Keeping these values with sstables also fixes
an edge case where you could leak repaired data back into unrepaired if you run full and incremental
repairs concurrently.



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

Mime
View raw message