cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-157) make cassandra not allow itself to run out of memory during sustained inserts
Date Sat, 09 May 2009 00:44:45 GMT

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

Jonathan Ellis commented on CASSANDRA-157:
------------------------------------------

if you're running out of memory, start by decreasing these settings in conf/storage-conf.
 svn up first because objectcount used to default to 0.1 (i.e. 100k objects).

    <!--
      The maximum amount of data to store in memory before flushing to
      disk. Note: There is one memtable per column family, and this threshold
      is based solely on the amount of data stored, not actual heap memory
      usage (there is some overhead in indexing the columns).
    -->
    <MemtableSizeInMB>32</MemtableSizeInMB>

    <!--
      The maximum number of columns in millions to store in memory
      before flushing to disk.  This is also a per-memtable setting.
      Use with MemtableSizeInMB to tune memory usage.
    -->
    <MemtableObjectCountInMillions>0.02</MemtableObjectCountInMillions>



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


Mime
View raw message