[
https://issues.apache.org/jira/browse/CASSANDRA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992194#comment-12992194
]
Brandon Williams commented on CASSANDRA-2142:
---------------------------------------------
Part of the problem there is the heap size of 128M is ridiculously small and
you can insert data quickly enough that CMS probably never gets a chance before
it goes into the death spiral I'm seen around 90% on various (1G+) heaps. The
threshold is too high though, although this may ultimately depend on how much
breathing room is left in the heap (and thus the size of the heap itself.)
> 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.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
