You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "DOAN DuyHai (JIRA)" <ji...@apache.org> on 2016/03/18 20:43:34 UTC
[jira] [Created] (CASSANDRA-11383) SASI index build leads to
massive OOM
DOAN DuyHai created CASSANDRA-11383:
---------------------------------------
Summary: SASI index build leads to massive OOM
Key: CASSANDRA-11383
URL: https://issues.apache.org/jira/browse/CASSANDRA-11383
Project: Cassandra
Issue Type: Bug
Components: CQL
Environment: C* 3.4
Reporter: DOAN DuyHai
Attachments: system.log_sasi_build_oom
13 bare metal machines
- 6 cores CPU (12 HT)
- 64Gb RAM
- 4 SSD in RAID0
JVM settings:
- G1 GC
- Xms32G, Xmx32G
C* settings:
- concurrent_compactors: 1
- compaction_throughput_mb_per_sec: 256
I created 9 SASI indices
- 8 indices with text field, NonTokenizingAnalyser, PREFIX mode, case-insensitive
- 1 index with numeric field, SPARSE mode
After a while, the nodes just gone OOM.
I attach log files. You can see a lot of GC happening while index segments are flush to disk. At some point the node OOM ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)