[CASSANDRA-12662] OOM when using SASI index

• Type: Bug
• Status: Open
• Priority: Urgent
• Resolution: Unresolved
• Fix Version/s: 3.11.x
• Component/s: Feature/SASI

Environment

Linux, 4 CPU cores, 16Gb RAM, Cassandra process utilizes ~8Gb, of which ~4Gb is Java heap

• Severity: Critical
• Assignee: Unassigned
• Reporter: Maxim Podkolzine
• Created: 18/Sep/16 16:26
• Updated: 24/Aug/20 09:48

Description

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?

Issue Links

• is related to: CASSANDRA-16071 max_compaction_flush_memory_in_mb is interpreted as bytes