You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2020/04/02 12:20:00 UTC

[jira] [Assigned] (CASSANDRA-12701) Repair history tables should have TTL and TWCS

     [ https://issues.apache.org/jira/browse/CASSANDRA-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson reassigned CASSANDRA-12701:
-------------------------------------------

    Assignee: Marcus Eriksson

> 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: Legacy/Core
>            Reporter: Chris Lohfink
>            Assignee: Marcus Eriksson
>            Priority: Normal
>              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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org