[
https://issues.apache.org/jira/browse/CASSANDRA-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533008#comment-15533008
]
Alex Petrov commented on CASSANDRA-12662:
-----------------------------------------
20Gb per node should be quite fine. Did you try configuring
{{memtable_*heap_space_in_mb}} (which is 1/4 heap by default) and
{{memtable_cleanup_threshold}}. So technically 4Gb partition updates is still
"under" the threshold. Problem is that there's some memory (also, CPU) involved
into the flush process, so making it lower should help.
> OOM when using SASI index
> -------------------------
>
> Key: CASSANDRA-12662
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12662
> Project: Cassandra
> Issue Type: Bug
> Environment: Linux, 4 CPU cores, 16Gb RAM, Cassandra process utilizes
> ~8Gb, of which ~4Gb is Java heap
> Reporter: Maxim Podkolzine
> Assignee: Alex Petrov
> Priority: Critical
> Fix For: 3.x
>
> Attachments: memory-dump.png
>
>
> 2.8Gb of the heap is taken by the index data, pending for flush (see the
> screenshot). As a result the node fails with OOM.
> Questions:
> - Why can't Cassandra keep up with the inserted data and flush it?
> - What resources/configuration should be changed to improve the performance?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
