cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Caleb Rackliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12662) OOM when using SASI index
Date Sat, 14 Jan 2017 05:51:26 GMT


Caleb Rackliffe commented on CASSANDRA-12662:

[~mkrupits_jb] Have you tried attaching {{strace}} to the running Cassandra process to track
down the specific reason for the mapping failure? For instance, the {{ENOMEM}} error code
could just mean Cassandra is mapping too many files. (The limit is usually enforced by the
kernel in {{/proc/sys/vm/max_map_count}}.)

> OOM when using SASI index
> -------------------------
>                 Key: CASSANDRA-12662
>                 URL:
>             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.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

View raw message