Hi,
I've not seen the thread dump from the node with order 3:
'CAA9E3DB-266B-4040-B059-19BD281D5821'
(corresponds to log: ignite-caa9e3db.0.log) and from other nodes too.
It may hep a lot if the thread dumps are created when the query hangs.
Server node + client app thread dumps - the best info.
But JDBC was connected to this node (looks like the nodes' logs).
The described case is not clear for me.
But i see a lot of strange log messages at the node with order 3:
[...][WARNING][grid-nio-worker-client-listener-0-#30][ClientListenerProcessor]
Closing NIO session because of unhandled exception [cls=class
o.a.i.i.util.nio.GridNioException, msg=Operation timed out]
[...][SEVERE][grid-nio-worker-client-listener-0-#30][ClientListenerProcessor]
Closing NIO session because of unhandled exception.
class org.apache.ignite.IgniteCheckedException: Invalid handshake message
[...][WARNING][grid-nio-worker-tcp-comm-2-#26][TcpCommunicationSpi]
Unknown connection detected (is some other software connecting to this
Ignite port?) [rmtAddr=/x.x.x.x]
It looks like:
- some network clients/services are configured invalid.
- someone tried to hack you. Is not it?. %)
On 12.02.2020 8:31, pg31 wrote:
Hi
Thank You for the reply Denis.
Please find the logs attached. The query was still running
Create_IDX_Stuck.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/t2770/Create_IDX_Stuck.zip>
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
--
Taras Ledkov
Mail-To: [email protected]
