heap dump generation does not seems to be working.
whenever I tried to generate the heap dump, node is going down, bit strange,
what else we could analyze
On Tue, Oct 12, 2021 at 7:35 PM Zhenya Stanilovsky
wrote:
> hi, highly likely the problem in your code - cpu usage grow synchronously
> with
hi, highly likely the problem in your code - cpu usage grow synchronously with
heap increasing between 00.00 and 12.00.
You need to analyze heap dump, no additional settings will help here.
>On the same subject, we have made the changes as suggested
>
>nodes are running on 8 CORE and 128 GB M
Ok, i still can`t understand whats the source of 128 value.
Can you check Runtime.getRuntime().availableProcessors() returning value on
your side ?
>
>>
>>>Hi Naveen,
>>>
>>>my first change was to change jvm parameters, at first it seemed to be
>>>resolved but changing jvm parameters only
yes i was able to get 128 with the following configuration;
here is a sample log;
[2021-09-27T00:00:19,359][INFO ][grid-timeout-worker-#198][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=f0025abe, uptime=2 days, 21:40:21.138]
^-- Cluster [h
systemThreadPoolSize and other pools are defined by default from:
Runtime.getRuntime().availableProcessors(), if you somehow obtain 128, plz fill
the ticket with all env info.
thanks !
>after many configuration changes and optimizations, i think i've solved the
>heap problem.
>
>here are th
