[ https://issues.apache.org/jira/browse/CASSANDRA-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196954#comment-16196954 ]
Aleksey Yeschenko commented on CASSANDRA-12701: ----------------------------------------------- CASSANDRA-13813 has implications on the workaround suggested here. I favour tackling CASSANDRA-13813 independently, and finding a way to correct CASSANDRA-12701 in this JIRA, without blocking the former on the latter. If you feel the same, or otherwise, or have a third option, please let your opinion known in CASSANDRA-13813 comments. Cheers. > Repair history tables should have TTL and TWCS > ---------------------------------------------- > > Key: CASSANDRA-12701 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12701 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Chris Lohfink > Labels: lhf > Attachments: CASSANDRA-12701.txt > > > Some tools schedule a lot of small subrange repairs which can lead to a lot > of repairs constantly being run. These partitions can grow pretty big in > theory. I dont think much reads from them which might help but its still > kinda wasted disk space. I think a month TTL (longer than gc grace) and maybe > a 1 day twcs window makes sense to me. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org