cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10280) Make DTCS work well with old data
Date Thu, 26 Nov 2015 14:54:11 GMT

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

Paulo Motta commented on CASSANDRA-10280:
-----------------------------------------

Just for the record {{max_window_size_seconds}} property broke some trivial cqlsh completion
tests, which is fixed on CASSANDRA-10753.

> 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
>              Labels: docs-impacting
>             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)

Mime
View raw message