Hi Sumit,
Sorry, for late answer.
Yes. Possibly there is a memory leak in some cases on ignite-1.7.
Try to switch to newer version.
Please, ignore if it is not actual any more.
--
Best regards,
Andrey V. Mashenkov
any help here ?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/heap-dump-on-ignite-servers-tp15679p16089.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Thank you Andrew.. we are upgrading Ignite to 2.0 so hopefully we wont have
such issues.
On Wed, Jul 26, 2017 at 10:35 AM, Andrew Mashenkov [via Apache Ignite
Users] wrote:
> Hi,
>
> Looks like we have a more optimal code in latest versions. See IGNITE-4154
>
Hi,
Looks like we have a more optimal code in latest versions. See IGNITE-4154
[1]
Try to update to >= 1.8 version.
As a workaround you can try to reduce discovery history size with JVM
option IGNITE_AFFINITY_HISTORY_SIZE, which is 500 by default.
[1]