cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12300) Disallow unset memtable_cleanup_threshold when flush writers is set
Date Thu, 08 Sep 2016 17:51:20 GMT

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

Benedict commented on CASSANDRA-12300:
--------------------------------------

Heh, funny how many places that advice has been declared awful (I apparently did so 15 months
ago in CASSANDRA-9274) and yet it persists....

> Disallow unset memtable_cleanup_threshold when flush writers is set
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-12300
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12300
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brandon Williams
>
> Many times I see flush writers set, and mct unset, leading to a very small mct, which
causes unneeded frequent flushing, and then of course compaction.  I also think the default
is a bit conservative, typically ending up at 0.11, where I'd say the majority of use cases
only have one or two hot tables and are much better served at 0.7 or 0.8.



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

Mime
View raw message