Re: Client stuck on startup

Hello! It is possible that Linux is more lenient towards creation of massive number of threads. Regards, -- Ilya Kasnacheev ср, 13 янв. 2021 г. в 19:44, VeenaMithare : > Let me debug this a bit more. Also I will try and capture another set of > thread dumps when this occurs again. This issue

Re: Client stuck on startup

Let me debug this a bit more. Also I will try and capture another set of thread dumps when this occurs again. This issue occurs on my windows machine sometimes - doesnt happen all the time. I have not seen this on my linux env. yet. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client stuck on startup

I dont think the server dumps were taken after the client disconnected . They were taken when the client was in the stuck state. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client stuck on startup

Hello! But are they collected after the client node has already left? Not to mention that server nodes too have an obscene number of threads, and as such are vulnerable to the same problem. Regards, -- Ilya Kasnacheev ср, 13 янв. 2021 г. в 18:25, VeenaMithare : > Hello, > > Thread dump from t

Re: Client stuck on startup

Hello, Thread dump from the server nodes has been provided in the original post, regards, Veena -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client stuck on startup

Hello! Please provide full thread dump from server nodes. Of course, you will need to kill client JVM first. Regards, -- Ilya Kasnacheev ср, 13 янв. 2021 г. в 17:09, VeenaMithare : > > a. If you see the thread dump, it shows these locked synchronizers >Locked ownable synchronizers: >

Re: Client stuck on startup

a. If you see the thread dump, it shows these locked synchronizers Locked ownable synchronizers: - <0x0006da73f540> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) - <0x0006da73f690> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)

Re: Client stuck on startup

Hello! I'm not sure what happens on the server nodes. Restarting the JVM with this client should be enough. Regards, -- Ilya Kasnacheev вт, 12 янв. 2021 г. в 19:14, VeenaMithare : > Okay, thanks Ilya . After it gets this issue, the app doesnt startup till > I > restart my server nodes. > > I

Re: Client stuck on startup

Okay, thanks Ilya . After it gets this issue, the app doesnt startup till I restart my server nodes. Is there anyway I can ensure clean shutdown when I face issues like this ? It looks like some ignite state is not cleaned up . regards, Veena. -- Sent from: http://apache-ignite-users.70518

Re: Client stuck on startup

Hello! Shutdown hook means that JVM decided to stop. Probably due to thread creation error if you ask me. It seems that the node has never finished initialization, judging by that log. Regards, -- Ilya Kasnacheev пн, 11 янв. 2021 г. в 19:25, VeenaMithare : > >>Try to use some realistic value

Re: Client stuck on startup

>>Try to use some realistic value such as 64. I think it hadnt worked earlier - I will try again. client-log.txt Please find the client log file attached. I am seeing 'invoking shutdown hook..' as an INFO in the startup

Re: Client stuck on startup

Hello! I don't know since it's impossible to check thread dump with such a high number of threads. I suspect it's possible. I also don't see any log for client, only thread dump. Can you attach it as well? Try to use some realistic value such as 64. Regards, -- Ilya Kasnacheev пн, 11 янв. 202

Re: Client stuck on startup

This client is a sync which syncs around 1 million records from our old db to ignite . When I start the application, it runs the initial sync and I need a higher striped pool. I think the client sees starvation in striped thread pool when I give a small thread pool. ( I dont have the logs for the

Re: Client stuck on startup

Hello! Are you sure that you really need a 1024 thread striped pool? What happens if it's only 16? Regards, -- Ilya Kasnacheev пн, 11 янв. 2021 г. в 17:55, VeenaMithare : > HI , > > One of the clients on my windows box sometimes gets stuck up on startup . > I > see this in the thread dump of

Client stuck on startup

HI , One of the clients on my windows box sometimes gets stuck up on startup . I see this in the thread dump of the client. a. Not sure what those locked synchronizers are "main" #1 prio=5 os_prio=0 tid=0x02c9c800 nid=0x4404 waiting on condition [0x02c8e000] java.lang.Thr