[
https://issues.apache.org/jira/browse/CASSANDRA-11383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202259#comment-15202259
]
DOAN DuyHai edited comment on CASSANDRA-11383 at 3/18/16 10:11 PM:
-------------------------------------------------------------------
[~xedin]
OK, I'm trying to fetch the sstable with its data files
In the meantime, I just re-create one index as shown above using
*max_compaction_flush_memory_in_mb* = 128 and SASI flushes thousands of index
files (of ~16kb each) and eventually the server dies maybe because too many
file handles
{noformat}
INFO [SASI-General:1] 2016-03-18 22:45:37,480 PerSSTableIndexWriter.java:258 -
Flushed index segment
/home/cassandra/data/sharon/resource_bench-4d065db0ebbc11e5995bd129cfce5717/ma-1831-big-SI_resource_period_end_month_int_idx.db_130370,
took 0 ms.
INFO [SASI-General:1] 2016-03-18 22:45:37,581 PerSSTableIndexWriter.java:258 -
Flushed index segment
/home/cassandra/data/sharon/resource_bench-4d065db0ebbc11e5995bd129cfce5717/ma-1831-big-SI_resource_period_end_month_int_idx.db_130371,
took 101 ms.
ERROR [SASI-General:1] 2016-03-18 22:45:37,582 CassandraDaemon.java:195 -
Exception in thread Thread[SASI-General:1,5,main]
org.apache.cassandra.io.FSReadError: java.io.IOException: Map failed
{noformat}
was (Author: doanduyhai):
[~xedin]
OK, I'm trying to fetch the sstable with its data files
In the meantime, I just re-create one index as shown above using *
max_compaction_flush_memory_in_mb * = 128 and SASI flushes thousands of index
files and eventually the server dies maybe because too many file handles
{noformat}
INFO [SASI-General:1] 2016-03-18 22:45:37,480 PerSSTableIndexWriter.java:258 -
Flushed index segment
/home/cassandra/data/sharon/resource_bench-4d065db0ebbc11e5995bd129cfce5717/ma-1831-big-SI_resource_period_end_month_int_idx.db_130370,
took 0 ms.
INFO [SASI-General:1] 2016-03-18 22:45:37,581 PerSSTableIndexWriter.java:258 -
Flushed index segment
/home/cassandra/data/sharon/resource_bench-4d065db0ebbc11e5995bd129cfce5717/ma-1831-big-SI_resource_period_end_month_int_idx.db_130371,
took 101 ms.
ERROR [SASI-General:1] 2016-03-18 22:45:37,582 CassandraDaemon.java:195 -
Exception in thread Thread[SASI-General:1,5,main]
org.apache.cassandra.io.FSReadError: java.io.IOException: Map failed
{noformat}
> 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: CASSANDRA-11383.patch, new_system_log_CMS_8GB_OOM.log,
> 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
> Data set:
> - ≈ 100Gb/per node
> - 1.3 Tb cluster-wide
> - ≈ 20Gb for all SASI indices
> C* settings:
> - concurrent_compactors: 1
> - compaction_throughput_mb_per_sec: 256
> - memtable_heap_space_in_mb: 2048
> - memtable_offheap_space_in_mb: 2048
> 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 ...
> /cc [~xedin]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
