[jira] Commented: (CASSANDRA-401) Less crappy failure mode when swamped with inserts than "run out of memory and gc-storm to death"

["Jeff Hammerbacher (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749217#action_12749217 ] 

Jeff Hammerbacher commented on CASSANDRA-401:
---------------------------------------------

Hey Sam,

If you are performing a bulk load, you may want to check out the Binary Memtable path that was recently excavated by Chris Goffinet: http://github.com/lenn0x/Cassandra-Hadoop-BMT/tree/master. Essentially it's a MapReduce job that writes data in the format it will take on disk to make compactions cheap, quite similar to the work from the PNUTS team at SIGMOD 2008 (http://portal.acm.org/citation.cfm?id=1376693).

The problem described in this ticket certainly remains when one performs many insertions via the standard API, of course.

Later,
Jeff

> 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.