cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12701) Repair history tables should have TTL and TWCS
Date Wed, 12 Oct 2016 14:38:21 GMT

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

Jeremiah Jordan commented on CASSANDRA-12701:
---------------------------------------------

For the upgrade scenario users will need to update the settings themselves, which they can
already do.  Because of the fact that users could have already made similar changes to these
tables we can't modify them ourselves during an update.
We probably need a NEWS.txt entry here recommending people to do that, and also that they
may want to delete the old data from the table before the TTL was applied, though there isn't
really a good way to do that :/.

> 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)

Mime
View raw message