[
https://issues.apache.org/jira/browse/CASSANDRA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755700#action_12755700
]
Jonathan Ellis commented on CASSANDRA-401:
------------------------------------------
The MemoryPoolMXBean approach is going to be JVM and even GC implementation
specific, right? For instance right now I have CMS old gen, CMS perm gen, code
cache, par eden space, and par survivor space memory pools with the JDK6 CMS
GC. But with the throughput GC, or JDK7 G1, those would be different. So
picking a single pool and setting a threshold seems fragile, and so does taking
the average or max of all pools.
> Less crappy failure mode when swamped with inserts than "run out of memory
> and gc-storm to death"
> -------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-401
> URL: https://issues.apache.org/jira/browse/CASSANDRA-401
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Fix For: 0.5
>
> Attachments: screenshot-1.jpg
>
>
> Suggestion was made that
> http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryPoolMXBean.html#setCollectionUsageThreshold(long)
> is relevant. Correlation eludes me, but I Am Not A Java Expert. :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
