[ 
https://issues.apache.org/jira/browse/CASSANDRA-11383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DOAN DuyHai updated CASSANDRA-11383:
------------------------------------
    Description: 
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]

  was:
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
- 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]


> 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
> 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)

Reply via email to