Maxim Podkolzine created CASSANDRA-12662:

             Summary: OOM when using SASI index
                 Key: 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: Critical
             Fix For: 3.6
         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.

- 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

Reply via email to