Hello! Don't see any logs here.
This setting may be problematic because you consume 14 out of 16GB by a single Ignite process so system may decide to swap something out. I recommend decreasing heap to 2G if possible. Should also make GC faster. I'm not sure how to enable GC logs when running a package. Regards, -- Ilya Kasnacheev ср, 28 авг. 2019 г. в 17:21, John Smith <[email protected]>: > Hi I have attached some details here: > https://www.dropbox.com/s/etm61xeb9mghs9m/ignite-details.log?dl=0 > > How do I enable GC logs? I'm running the Debian package. > > In summary: > 1- Only ignite is running on the host > 2- Ignite is configured to use 4GB heap > 3- Host has 16GB total > 4- 10GB off-heap configured > 5- Above is same for all 3 hosts > > On Wed, 28 Aug 2019 at 08:28, Ilya Kasnacheev <[email protected]> > wrote: > >> Hello! >> >> It's hard to say what happens here. Do you have GC log? Please make sure >> to collect it. >> >> Is there anything running in the same JVM with Ignite? >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> ср, 28 авг. 2019 г. в 15:13, John Smith <[email protected]>: >> >>> I'm not doing anything fancy with the cache I have 3 million records >>> partitioned cache over 3 servers. And all I do is some put and gets. Unless >>> I have a bad config? >>> >>> On Wed., Aug. 28, 2019, 6:32 a.m. Ilya Kasnacheev, < >>> [email protected]> wrote: >>> >>>> Hello! >>>> >>>> Well, it's pretty descriptive. Node was dropped from topology because >>>> of long GC pauses. >>>> >>>> Either find ways to decrease GC pauses, or increase >>>> failureDetectionTimeout. >>>> >>>> Regards, >>>> -- >>>> Ilya Kasnacheev >>>> >>>> >>>> ср, 28 авг. 2019 г. в 00:18, John Smith <[email protected]>: >>>> >>>>> Hi, running 2.7.0 >>>>> >>>>> I noticed one of my nodes was down. It seems to have turned itself >>>>> off, because of: Ignite node is in invalid state due to a critical >>>>> failure. >>>>> >>>>> I attached logs here: >>>>> https://www.dropbox.com/s/82li1020a5ig4ty/ignite-failled.log?dl=0 >>>>> >>>>
