Hi,
We were executing few SQL queries on Apache Ignite to test the performance
using JDBC.
Connection con =
DriverManager.getConnection("jdbc:ignite:cfg://cache=XYZ_CACHE:distributedJoins=false@file:///C:\\ignite-client-config-with-timeout.xml");
We had an interim network glitch and the query processing had stopped and we
waited for the client to re-establish connection to the server. Guess there
was a prolonged n/w glitch the connection re-establishment did not happen.
Post that , when we tried to re-run the program to establish client
connection , we could find from server logs that the connection
establishment was successful but on the client side, it was waiting for an
ACK.
Please find the logs below --
[14:38:07,480][INFO][grid-timeout-worker-#69%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=76a6ee56, name=null, uptime=47:47:36:573]
^-- H/N/C [hosts=4, nodes=4, CPUs=16]
^-- CPU [cur=1%, avg=0.39%, GC=0.53%]
^-- Heap [used=235MB, free=94.26%, comm=1024MB]
^-- Non heap [used=37MB, free=-1%, comm=318MB]
^-- Public thread pool [active=0, idle=32, qSize=0]
^-- System thread pool [active=32, idle=0, qSize=17]
^-- Outbound messages queue [size=0]
[14:38:08,387][INFO][disco-event-worker-#84%null%][GridDiscoveryManager]
Added new node to topology: TcpDiscoveryNode
[id=63a97c08-ded9-4ca7-b3fd-230ef0309906, addrs=[0:0:0:0:0:0:0:1, X.X.X.X,
127.0.0.1], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /X.X.X.X:0],
discPort=0, order=81, intOrder=43, lastExchangeTime=1480496888341,
loc=false, ver=1.7.0#19700101-sha1:00000000, isClient=true]
[14:38:08,390][INFO][disco-event-worker-#84%null%][GridDiscoveryManager]
Topology snapshot [ver=81, servers=3, clients=2, CPUs=16, heap=14.0GB]
[14:38:08,392][INFO][exchange-worker-#87%null%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=81, minorTopVer=0], evt=NODE_JOINED,
node=63a97c08-ded9-4ca7-b3fd-230ef0309906]
We could see that the *System thread pool* [active=32, idle=0, qSize=17].
Please let us know a way to clear the *System thread pool* without having to
restart the server.
Also, we are curious to know the reason for such a scenario to arise. Any
insight will be of great assistance.
Thanks,
Ganesh
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-establish-connection-to-Ignite-server-tp9294.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
