Hi, It looks like the issue described in https://issues.apache.org/jira/browse/IGNITE-11953 There a two options: 1. I believe it will be fixed very soon. Thus you could create a build based on 2.7.5 with cherry-picked fix. 2. You could remove the cachegroup property from the cache configuration. In this case you have to start a new cluster and it requires much more heap memory on the startup since there are about 650 caches.
Thanks, Pavel сб, 13 июл. 2019 г. в 18:18, ihalilaltun <[email protected]>: > Hi Igniters, > > Recently (11.07.2019), we have upgraded our ignite versin from 2.7.0 to > 2.7.5. Just like after 11 hours one of our nodes killed itself without any > notification. I am adding the details that I could get from the server and > the topology we use; > > *Ignite version*: 2.7.5 > *Cluster size*: 16 > *Client size*: 22 > *Cluster OS version*: Centos 7 > *Cluster Kernel version*: 4.4.185-1.el7.elrepo.x86_64 > *Java version* : > openjdk version "1.8.0_212" > OpenJDK Runtime Environment (build 1.8.0_212-b04) > OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode) > > By the way this is a production environment and we have been using this > topology for almost 5 months. Our average tps size is ~5000 for the > cluster. > We have 8 to 10 different object that we persist on ignite, some of them > relatively big and some ara just strings. > > ignite.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/t2515/ignite.zip> > gc.current > <http://apache-ignite-users.70518.x6.nabble.com/file/t2515/gc.current> > hs_err_pid18537.log > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2515/hs_err_pid18537.log> > > > > > > ----- > İbrahim Halil Altun > Senior Software Engineer @ Segmentify > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Regards Pavel Vinokurov
