Re: Database has been closed

[Ilya Kasnacheev <il...@gmail.com>]

Hello!

Unfortunately, we can't go from here without thread dump or, at least, a
complete log from the beginning.

Regards,
-- 
Ilya Kasnacheev


чт, 25 февр. 2021 г. в 11:07, DonTequila <do...@gmx.de>:

> Hi again,
>
> is there anything that could help me identify the potential reason for the
> read lock timout without having a thread dump? Are there settings that I
> can
> tune to increase this timeout and prevent from the node/database to close?
>
> Thanks.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Database has been closed

[Ilya Kasnacheev <il...@gmail.com>]

Hello!

You don't seem to have INFO log level enabled, so there's not much to see
there unfortunately. Please enable INFO level, it should also add thread
dumps automatically, I think.

Regards,
-- 
Ilya Kasnacheev


пн, 1 мар. 2021 г. в 13:48, DonTequila <do...@gmx.de>:

> Hi Ilya,
>
> The complete log is with the link below, can you take a look:
> ignite-2dc05669.gz
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2401/ignite-2dc05669.gz>
>
>
> I will try to add code that dumps stacktrace and threads in such cases, but
> I'm not sure yet how to do this.
>
> Thanks,
> Thomas.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Database has been closed

[DonTequila <do...@gmx.de>]

Hi Ilya,

The complete log is with the link below, can you take a look:
ignite-2dc05669.gz
<http://apache-ignite-users.70518.x6.nabble.com/file/t2401/ignite-2dc05669.gz>  

I will try to add code that dumps stacktrace and threads in such cases, but
I'm not sure yet how to do this.

Thanks,
Thomas.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/