Hello,
Thanks for your response,
Yes, both the servers are on.
Thanks & Regards,
Charlin
On Thu, 1 Apr 2021 at 20:29, Ilya Kasnacheev
wrote:
> Hello!
>
> What is your baseline topology? Are both of your server nodes on it?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 1 апр. 2021 г. в 07:02, C
Hi there
Il giorno dom 4 apr 2021 alle ore 21:39 DonTequila ha
scritto:
> Hi,
>
> thanks for your suggestions. Unfortunately this didn't help improving the
> startup time.
>
I only had such slow startup times because of the two problems I described
before.
I had a look at your logs and there's
Actually I found that this is indeed true. Ignite supports the JRE option:
-DIGNITE_NO_SHUTDOWN_HOOK=true
When I set this my app shutdown hook has enough time to call deactive the
cluster.
I wonder if this is safe to do?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
No, this is happening for the last server node with no other nodes connected.
To me it looks like Ignite itself is already handling its own shutdown hook
when SIGTERM is sent and then internally starts disconnect. So Ignite
doesn't allow deactivate any more. Is this possible true?
--
Sent from:
Hi,
thanks for your suggestions. Unfortunately this didn't help improving the
startup time.
Looking at the log it takes most of the time (about 9 minutes) here:
23-03-2021 14:34:38.424 [ 1] INFO GridCacheProcessor
Started cache in recovery mode [name=MediaFan_Jobs, id=
