[
https://issues.apache.org/jira/browse/CASSANDRA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2142:
--------------------------------------
Attachment: 2142-v2.txt
Tha makes sense: 1.0-threshold needs to be enough heap remaining that the flush
can complete before you finish running out and dying.
v2 splits the threshold into flush_largest_memtables_at and reduce_cache_sizes
at, and reduces flush threshold in .yaml to 0.75 (= our default
CMSInitiatingOccupancyThreshold, which is the lowest it's going to do any good
at.)
v2 initializes GCInspector before CL.recover so it can be useful there.
v2 also adjusts log messages to clarify that we don't flush the same MT twice.
> Add "reduce memory usage because I tuned things poorly" feature
> ---------------------------------------------------------------
>
> Key: CASSANDRA-2142
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2142
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Labels: ponies
> Fix For: 0.7.1
>
> Attachments: 2142-v2.txt, 2142.txt
>
>
> Users frequently create too many columnfamilies, set the memtable thresholds
> too high (or adjust throughput while ignoring operations), and/or set caching
> thresholds too high. Then their server OOMs and they tell their friends
> Cassandra sucks.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
