Hi Gianluca Bonetti - Initially if I restart when the data is around 100
million entries, it takes about 3 minutes, now I am testing it with 270
million and it takes about 12 minutes. Upon looking into the ignite code,
this is where its taking time in the class
org.apache.ignite.internal.IgntionEx
I don’t think you should be activating the cluster every time you restart a
node. Generally it’s best to activate the cluster once and manage the baseline
topology “manually” after that.
> On 7 Apr 2020, at 17:20, krkumar24061...@gmail.com wrote:
>
> Hi Gianluca Bonetti - Thanks for the help.
Hello Krumar
Full explanation about the slowness when using AlwaysPreTouch comes from
this article https://access.redhat.com/solutions/2685771
Is it still taking 5 minutes to start, after removing the AlwaysPreTouch
parameter?
Cheers
Gianluca
Il giorno mar 7 apr 2020 alle ore 18:20
Hi Gianluca Bonetti - Thanks for the help. I actually have that JVM parameter
and now I have removed that. Looks like its working and I will do few more
rounds of testing and then update you.
Also any idea why ignite.active(true) taking almost 5 minutes whenever i
restart the node?
Again a big
Hello Kumar
It seems a problem similar to the one I had in the past.
Please check that you are running the JVM *without* the
"-XX:+AlwaysPreTouch" parameter.
Also, in my experience, using /dev/random as entropy source could block
startup for long time, hence I prefer using /dev/urandom
(set
Hi Guys - I have this problem that's very recent and nothing significant
changed in the system but all of a sudden still takes lot of time to
restart. I do a graceful shutdown of one of the nodes and restart the node
after some updates. Now the ignite takes almost 30 minutes to initiate and
that's
