[
https://issues.apache.org/jira/browse/CASSANDRA-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555464#comment-15555464
]
Jeff Jirsa commented on CASSANDRA-12701:
----------------------------------------
Patch is fine. If you do a PR on Github, the committer is going to need to turn
it into a patch, anyway, to merge it to the appropriate branch(es), because
github is read-only (writable repo is at ASF not github). I've only pushed it
to my github so I could kick off tests (which look good).
> 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.3.4#6332)
