You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2015/07/06 16:29:04 UTC

[jira] [Commented] (CASSANDRA-9130) reduct default dtcs max_sstable_age

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

Jeff Jirsa commented on CASSANDRA-9130:
---------------------------------------

I know this sounds obvious, but I'm repeating it for the record, because it's relevant:

You will still introduce fragmentation during bootstrap, bulk load, and decom, potentially thousands or tens of thousands of sstables per node for decom.

Lowing max_sstable_age_days below the table TTL is not necessarily safe, with or without CASSANDRA-9056







> reduct default dtcs max_sstable_age
> -----------------------------------
>
>                 Key: CASSANDRA-9130
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9130
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 3.x, 2.1.x, 2.0.x
>
>
> Now that CASSANDRA-9056 is fixed it should be safe to reduce the default age and increase performance correspondingly.  [~jshook] suggests that two weeks may be appropriate, or we could make it dynamic based on gcgs (since that's the window past which we should expect repair to not introduce fragmentation anymore).



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