[
https://issues.apache.org/jira/browse/CASSANDRA-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024005#comment-15024005
]
Marcus Eriksson commented on CASSANDRA-10280:
---------------------------------------------
fix versions are 2.1.12, 2.2.4, 3.0.1 and 3.1
bq. 1. Change DEFAULT_MAX_SSTABLE_AGE_DAYS to 1000 days. The patch says
365*1000, which is 365,000 days.
yes, 1000 years
bq. 2. Deprecate MAX_SSTABLE_AGE_DAYS. Note that it is deprecated.
yes
bq. 3. ADD DEFAULT_MAX_WINDOW_SIZE_SECONDS that is what size? The patch looks
like 1 day in seconds, or 86,400, but perhaps I misunderstand.
yes, default max window size is 1 day
> Make DTCS work well with old data
> ---------------------------------
>
> Key: CASSANDRA-10280
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10280
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 2.1.12, 2.2.4, 3.0.1, 3.1
>
>
> Operational tasks become incredibly expensive if you keep around a long
> timespan of data with DTCS - with default settings and 1 year of data, the
> oldest window covers about 180 days. Bootstrapping a node with vnodes with
> this data layout will force cassandra to compact very many sstables in this
> window.
> We should probably put a cap on how big the biggest windows can get. We could
> probably default this to something sane based on max_sstable_age (ie, say we
> can reasonably handle 1000 sstables per node, then we can calculate how big
> the windows should be to allow that)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
