[
https://issues.apache.org/jira/browse/CASSANDRA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716474#action_12716474
]
daishi commented on CASSANDRA-157:
----------------------------------
Sorry I haven't had a chance to follow up on this.
If I remember correctly the main unbounded memory growth
that caused OOMs did seem to go away, but that the exposed
properties didn't control the memory usage in a predictable way.
In particular I think the objCount property would schedule
a Memtable.flush(), but ColumnFamilyStore.memtablesPendingFlush
would be actually flushed according to a different schedule.
I haven't read enough of the code to know whether it would
be possible/make sense to allow user-control of latter schedule,
but that was the direction I was thinking in when I had to drop
this for a bit (maybe you can let me know if that makes no
sense or if there's a better way to think about things).
> 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.
