I've been having problems recently with nodes crashing out of a running, 18-node cluster. I managed to catch the following error log out of one of them. Unfortunately I did not manage to grab the core dump before the AWS instance was destroyed. I'll try to grab one if I can. This application in general has been running without problems like this for quite a while. We've started seeing these problems just in the last few weeks. I don't think there have been any major changes in how we interact with thee Ignite caches, but I need to do some more digging. FWIW we basically just use caches and compute colocation. We don't use anything fancy like SQL, joins, etc. ## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x00007f614e0f8f40, pid=79, tid=0x00007f5fc0139700## JRE version: Java(TM) SE Runtime Environment (8.0_152-b16) (build 1.8.0_152-b16)# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.152-b16 mixed mode linux-amd64 compressed oops)# Problematic frame:# J 29350 C2 org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/affinity/AffinityTopologyVersion;)V (186 bytes) @ 0x00007f614e0f8f40 [0x00007f614e0f8f20+0x20]## Core dump written. Default location: /usr/local/mycompany/myapp/core or core.79## An error report file with more information is saved as:# /usr/local/mycompany/myapp/hs_err_pid79.log## If you would like to submit a bug report, please visit:# http://bugreport.java.com/bugreport/crash.jsp#
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
