[
https://issues.apache.org/jira/browse/CASSANDRA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Pullara updated CASSANDRA-401:
----------------------------------
Attachment: screenshot-1.jpg
Cassandra continues to accept writes from a client even though it is getting
behind in flushing and compacting, eventually reaching GC thrash state and
stopping forward progress. You have to be very careful not to reach this state
when loading a lot of data. My suggestion was to use the MemoryPoolMXBean to
monitor the amount of heap available after a GC to ensure that you never get
into this state. You should like stop accepting writes from clients at that
point until the condition expires.
> 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.
