fe连接池异常,日志很多kill query timeout,版本3.0.3 #48696
Unanswered
hnie2010
asked this question in
A - General / Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
哪位高人帮忙瞧一瞧,是什么原因,怎么避免!连接很多,曾经出现多所有查询都hang住的情况!
2025-03-04 11:58:50,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.killByTimeout():980] kill time out query, remote: 10.221.1.106:48948, at the same time kill c
onnection is false, connection type: MYSQL, connectionId: 8038
2025-03-04 11:58:50,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.checkTimeout():1019] kill query timeout, remote: 10.221.7.50:35388, query timeout: 50000, que
ry id: TUniqueId(hi:4994782557913631267, lo:-5741566022815689534)
2025-03-04 11:58:50,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.killByTimeout():980] kill time out query, remote: 10.221.7.50:35388, at the same time kill co
nnection is false, connection type: MYSQL, connectionId: 8151
2025-03-04 11:58:51,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.checkTimeout():1019] kill query timeout, remote: 10.221.1.106:42018, query timeout: 50000, qu
ery id: TUniqueId(hi:4307247712773816650, lo:-6909497847364570807)
2025-03-04 11:58:51,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.killByTimeout():980] kill time out query, remote: 10.221.1.106:42018, at the same time kill c
onnection is false, connection type: MYSQL, connectionId: 7846
2025-03-04 11:58:51,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.checkTimeout():1019] kill query timeout, remote: 10.221.1.106:48948, query timeout: 50000, qu
ery id: TUniqueId(hi:9059590700894732387, lo:-6745521100139521548)
2025-03-04 11:58:51,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.killByTimeout():980] kill time out query, remote: 10.221.1.106:48948, at the same time kill c
onnection is false, connection type: MYSQL, connectionId: 8038
2025-03-04 11:58:51,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.checkTimeout():1019] kill query timeout, remote: 10.221.7.50:35388, query timeout: 50000, que
ry id: TUniqueId(hi:4994782557913631267, lo:-5741566022815689534)
2025-03-04 11:58:51,340 WARN (connect-scheduler-check-timer-0|145) [ConnectContext.killByTimeout():980] kill time out query, remote: 10.221.7.50:35388, at the same time kill co
nnection is false, connection type: MYSQL, connectionId: 8151
2025-03-04 11:58:51,462 WARN (mysql-nio-pool-246|145) [ConnectContext.kill():954] kill query from 10.221.15.135:42968, kill MYSQL connection: false
2025-03-04 11:58:51,463 WARN (mysql-nio-pool-246|145) [MysqlConnectProcessor.processOnce():399] Null packet received from network. remote: 10.221.15.135:57916
2025-03-04 11:58:51,463 WARN (mysql-nio-pool-246|145) [ReadListener.lambda$handleEvent$0():60] Exception happened in one session(org.apache.doris.qe.ConnectContext@38e0a2ae).
java.io.IOException: Error happened when receiving packet.
at org.apache.doris.qe.MysqlConnectProcessor.processOnce(MysqlConnectProcessor.java:400) ~[doris-fe.jar:1.2-SNAPSHOT]
at org.apache.doris.mysql.ReadListener.lambda$handleEvent$0(ReadListener.java:52) ~[doris-fe.jar:1.2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Beta Was this translation helpful? Give feedback.
All reactions