[
https://issues.apache.org/jira/browse/CASSANDRA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716482#action_12716482
]
Jonathan Ellis commented on CASSANDRA-157:
------------------------------------------
That's strange. Let me know if you can reproduce that behavior still with 0.3
or trunk. It shouldn't be queueing up unless the flusher is busy with a
different memtable.
> make cassandra not allow itself to run out of memory during sustained inserts
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-157
> URL: https://issues.apache.org/jira/browse/CASSANDRA-157
> Project: Cassandra
> Issue Type: Bug
> Reporter: daishi
> Assignee: daishi
> Attachments: Cassandra-157_Unregister_Memtable_MBean.diff
>
>
> Tv on IRC pointed out to me that the issue that I've been encountering
> is probably point 2. in this roadmap:
>
> http://www.mail-archive.com/[email protected]/msg00160.html
> I was unable to find any existing issue for this topic, so I'm creating a new
> one.
> Since this issue would block our use of Cassandra I'm happy to look into it,
> but if this is a known issue perhaps there's already a plan for addressing it
> that could be clarified?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
