Hello

It happened to me on a few occasions.
I have a couple of suggestions which may, or may not, solve your problem.
Please try :)

First, please ensure you use /dev/urandom as an entropy source.
/dev/random does a better job, but may cause long pauses (10 minutes or
longer may happen easier than expected) and /dev/urandom is good enough for
most cases.

Second, please ensure not to use -XX:+AlwaysPreTouch in your JVM flags as
zeroing large heaps on initialization may take a very long time.

Cheers
Gianluca

Il giorno mer 31 mar 2021 alle ore 21:12 DonTequila <[email protected]> ha
scritto:

> Has anyone been able to look at this and give me some advise? Thanks!
>
>
> DonTequila wrote
> > Hi,
> >
> > I'm seeing a pretty slow Ignite server node startup time, of approx
> > 20mins, with persistence enabled for most caches. Of course I can see
> > startup-time highly depends on disk speed, but I wonder if there are
> > settings that could improve this?
> >
> > I've attached a server log of the time when it starts. Also the Ignite
> > configs attached.
> >
> > Also, when first accessed from a client with SQL there's a long running
> > query which shouldn't be the case in my opinion for binary storage and
> > indexes?
> >
> > Can you spot anything that is wrong with my system startup time?
> >
> > Thanks,
> > Thomas.
> >
> >
> >
> >
> > server.log (102K)
> > &lt;
> http://apache-ignite-users.70518.x6.nabble.com/attachment/35676/0/server.log&gt
> ;
> > ignite-caches-config.xml (39K)
> > &lt;
> http://apache-ignite-users.70518.x6.nabble.com/attachment/35676/1/ignite-caches-config.xml&gt
> ;
> > ignite-caches-dataregions.xml (2K)
> > &lt;
> http://apache-ignite-users.70518.x6.nabble.com/attachment/35676/2/ignite-caches-dataregions.xml&gt
> ;
> > ignite-mediafan-db.xml (4K)
> > &lt;
> http://apache-ignite-users.70518.x6.nabble.com/attachment/35676/3/ignite-mediafan-db.xml&gt
> ;
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Reply via email to