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

[jira] Issue Comment Edited: (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:comment-tabpanel&focusedCommentId=12708121#action_12708121 ] 

Eric Evans edited comment on CASSANDRA-157 at 5/11/09 10:32 AM:
----------------------------------------------------------------

I think we need a wiki page which details what we've learned about tuning thresholds (and yes, I suppose I am volunteerin :).

      was (Author: urandom):
    I think we need a wiki page which details what we've learned about tuning thresholds to stay within memory constraints (and yes, I suppose I am volunteerin :).
  
> 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
>
> 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.