[ https://issues.apache.org/jira/browse/CASSANDRA-10013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713564#comment-14713564 ]
Jonathan Ellis commented on CASSANDRA-10013: -------------------------------------------- I suppose we could default it to min(4GB, 1/8 of free space) but man, 4GB total that's blink-and-you-missed-it territory. Are people actually doing that? Do we need to add a warning if we detect less than (say) 64GB free on startup? > 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 > Fix For: 2.1.x > > > 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)