Hi,
Sending a SIGQUIT signal forces VM to print a thread dump to its stdout:
kill -3
Stan
From: Justin Ji
Sent: 13 декабря 2018 г. 5:20
To: user@ignite.apache.org
Subject: Re: I encountered a problem when restarting ignite
Akurbanov -
Thank for your reply!
I have tried to dump the
Akurbanov -
Thank for your reply!
I have tried to dump the thread stacks, but I don't know how to dump the
thread stacks from a docker container since it only contains a simplified
JRE, does not have JSTACK tools, and I also googled a lot of information and
found that there is no suitable method.
Could you please provide logs from all nodes and jstack thread dumps?
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Sorry for forget the attachments.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I encountered a problem when restarting ignite, a node seems to be unable to
process the request anymore, because its CacheStore did not process the
update operations of database. Here is the log it printed:
2018-12-12 07:06:27:556 [exchange-worker-#42] WARN
Sorry for forgetting the attachments.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I encountered a problem when restarting ignite, a node seems to be unable to
process the request anymore, because its CacheStore did not process the
update operations of database. Here is the log it printed:
2018-12-12 07:06:27:556 [exchange-worker-#42] WARN
