[jira] [Commented] (CASSANDRA-12662) OOM when using SASI index

["Nirmal Singh KPS (Jira)" <ji...@apache.org>]

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

Nirmal Singh KPS commented on CASSANDRA-12662:
----------------------------------------------

Potentially indexes gonna involve more memory in a distributed data base like Cassandra.

It can index tables with less volume but not of big sizes. 

So creating indexes for big table should be questioned first , followed by if badly needed we can get typically faster machines with more RAM and force compaction to run faster on tables that needs to be indexed

> 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
>            Priority: Urgent
>             Fix For: 3.11.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
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org