[
https://issues.apache.org/jira/browse/CASSANDRA-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013730#comment-15013730
]
Branimir Lambov commented on CASSANDRA-10280:
---------------------------------------------
[DateTieredCompactionStrategyOptions
constructor|https://github.com/apache/cassandra/commit/7bb9ef4197c7e291f68af3a1493ff1d90ed2f121#diff-687b688750330c623a9a3df3f7a59e78R64]:
{{maxWindowSize}} is in the wrong unit, and should use the
{{DEFAULT_MAX_WINDOW_SIZE_SECONDS}} constant to avoid going out of sync.
Shouldn't {{max_window_size_seconds}} be validated as well?
> 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.x, 2.2.x, 3.x
>
>
> 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)
