cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-157) make cassandra not allow itself to run out of memory during sustained inserts
Date Tue, 28 Jul 2009 13:31:15 GMT

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

Hudson commented on CASSANDRA-157:
----------------------------------

Integrated in Cassandra #151 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/151/])
    use CSLS instead of NBHS for memtablesPendingFlush. See explanation here: http://sourceforge.net/tracker/?func=detail&aid=2828100&group_id=194172&atid=948362
patch by jbellis; reviewed by Brandon Williams for 


> 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
>          Components: Core
>            Reporter: daishi
>            Assignee: Jonathan Ellis
>         Attachments: 157.patch, 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.


Mime
View raw message