Re: ignite.active(true) blocking forever

Then you may have a data loss? --Yakov 2017-09-06 12:51 GMT+03:00 Вячеслав Коптилин : > Hi Yakov, > > At first sight, it seems that we can use the same approach for this issue, > but in this particular case, I think, the best way to handle > OutOfMemoryError is to

Re: ignite.active(true) blocking forever

Hi Yakov, At first sight, it seems that we can use the same approach for this issue, but in this particular case, I think, the best way to handle OutOfMemoryError is to shutdown the node that could not be activated. Best regards, Slava. 2017-09-06 11:26 GMT+03:00 Yakov Zhdanov

Re: ignite.active(true) blocking forever

Slava, this looks like the issue with start cache operation throwing exception on some nodes and cache start rollback. I remember you implemented that fix. Can we apply the same machinery to rollback the activation with proper exception? --Yakov

Re: ignite.active(true) blocking forever

Hi, I am sorry for the delay. I was able to reproduce this issue, and it looks like a bug. I created a jira ticket in order to track this https://issues.apache.org/jira/browse/IGNITE-6274 Thanks, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite.active(true) blocking forever

Hi Slava, Yes but in that case, at least the default jvm options should definitely work. -Xms128m -Xmx128m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=D:\GC -XX:OnOutOfMemoryError="kill -9 %p" The process is not getting killed and neither the heap dump is getting created. I have attached a

Re: ignite.active(true) blocking forever

Hi, I don't think there is a way to properly recover application/server or any other service once out of memory error arises. Just trying to send a simple notification may lead to another attempt to allocate memory and therefore new OOME must be thrown. So, the best way to treat OOME is to treat

Re: ignite.active(true) blocking forever

Thanks Slava, The recommended configuration worked for me. But I believe there is a much more seminal question here. If there is an error situation (OOM) why doesn't the server shutdown itself because had I not changed the config you recommended, I am not sure if the data grid server is even

Re: ignite.active(true) blocking forever

Hi, By default, each Ignite instance grabs 80% of available memory on startup, that may be a cause the operating system to start swapping and slows everything down. As you mentioned, you are trying to start 2 JVMs on same machine, so, it seems that you need to reduce memory size (it's a

ignite.active(true) blocking forever

Hi all, *QUESTION:-Is there a way to timeOut the ignite.active(true) so that the client does not block forever and moves ahead for some other important processing ?* *OBSERVATIONS:-* I have a client(-Xms512m -Xmx512m) which is represented by the following piece of code package