Hi Arthi,
Try to use Visual VM Memory Profiler to see the objects that fill the heap
[1]. Alternatively you can quickly build a heap histrogram ("jmap -histo
<java_process_pid>") that will show number of objects of a particular class
that are allocated.
There is a chance that your custom objects "leaked" somehow.
Next, setting Java heap to 50 GB is a wrong decision because it will lead to
enormous long GC pauses at sometime making your application unresponsive. By
setting this value you just shadowed the issue.
You can set generic VM settings and check them against your app [2].
If this issue still happens then:
- share the heap histogram or preferably Visual VM snapshot;
- GC logs. GC logs can be activated with the following properties
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps
-Xloggc:/{path_to_file}/gc.log
[1] https://visualvm.java.net/profiler.html
[2]
https://apacheignite.readme.io/docs/performance-tips#tune-garbage-collection
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-loading-errors-out-tp3636p3667.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
