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

Blake Eggleston commented on CASSANDRA-9143:
--------------------------------------------

bq. One approach would be to skip upfront anti-compaction if unrepaired set is 
above some size treshold

The larger a repair job is, the more likely it is you'll see inconsistencies 
cause by compaction. The cost of inconsistencies will increase as well. My 
thinking was that we would add something like {{Map<RepairSessionID, 
AbstractCompactionStrategy>}} to the compaction manager, and let the sstable 
silos work normally. I don't know if it would make sense, but we could use a 
noop strategy for jobs under some size threshold.

bq. some safety mechanism (timeout, etc) that releases sstables from the 
pending repair bucket

Seems reasonable

> Improving consistency of repairAt field across replicas 
> --------------------------------------------------------
>
>                 Key: CASSANDRA-9143
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9143
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>            Assignee: Blake Eggleston
>            Priority: Minor
>
> We currently send an anticompaction request to all replicas. During this, a 
> node will split stables and mark the appropriate ones repaired. 
> The problem is that this could fail on some replicas due to many reasons 
> leading to problems in the next repair. 
> This is what I am suggesting to improve it. 
> 1) Send anticompaction request to all replicas. This can be done at session 
> level. 
> 2) During anticompaction, stables are split but not marked repaired. 
> 3) When we get positive ack from all replicas, coordinator will send another 
> message called markRepaired. 
> 4) On getting this message, replicas will mark the appropriate stables as 
> repaired. 
> This will reduce the window of failure. We can also think of "hinting" 
> markRepaired message if required. 
> Also the stables which are streaming can be marked as repaired like it is 
> done now. 



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

Reply via email to