You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "daishi (JIRA)" <ji...@apache.org> on 2009/05/12 19:17:45 UTC

[jira] Updated: (CASSANDRA-157) make cassandra not allow itself to run out of memory during sustained inserts

     [ https://issues.apache.org/jira/browse/CASSANDRA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

daishi updated CASSANDRA-157:
-----------------------------

    Attachment: Cassandra-157_Unregister_Memtable_MBean.diff

This patch removes the MBean reference to Memtable objects,
reducing the memory pressure under sustained inserts somewhat.
(This helps, but I think there are other remaining issues).

> 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
>         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/cassandra-dev@incubator.apache.org/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.