[jira] [Updated] (CASSANDRA-10013) Default commitlog_total_space_in_mb to 4G

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-10013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-10013:
------------------------------------------
    Fix Version/s:     (was: 2.1.x)

> Default commitlog_total_space_in_mb to 4G
> -----------------------------------------
>
>                 Key: CASSANDRA-10013
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10013
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Brandon Williams
>
> First, it bothers me that we default to 1G but have 4G commented out in the config.
> More importantly though is more than once I've seen this lead to dropped mutations, because you have ~100 tables (which isn't that hard to do with OpsCenter and CFS and an application that uses a moderately high but still reasonable amount of tables itself) and when the limit is reached CLA flushes the oldest tables to try to free up CL space, but this in turn causes a flush stampede that in some cases never ends and backs up the flush queue which then causes the drops.  This leaves you thinking you have a load shedding situation (which I guess you kind of do) but it would go away if you had just uncommented that config line.



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