[fix](connection) kill connection when meeting Write mysql packet failed error #36559
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
morningman
changed the title
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 39707 ms |
TPC-DS: Total hot run time: 170636 ms |
ClickBench: Total hot run time: 30.91 s |
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 39593 ms |
TPC-DS: Total hot run time: 174014 ms |
ClickBench: Total hot run time: 31.32 s |
morningman
added a commit
that referenced
this pull request
Jun 20, 2024
zddr
approved these changes
Jun 21, 2024
iszhangpch
pushed a commit
to iszhangpch/doris-p
that referenced
this pull request
Jun 21, 2024
…led error (apache#36559) Some time we met error like: ``` 2024-06-15 17:26:16,492 WARN (mysql-nio-pool-206|11598) [ConnectProcessor.handleQueryException():420] Process one query failed because IOException: java.io.IOException: Write mysql packet failed.[write=646624, needToWrite=2097119] at org.apache.doris.mysql.MysqlChannel.realNetSend(MysqlChannel.java:407) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.mysql.MysqlChannel.flush(MysqlChannel.java:436) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.mysql.MysqlChannel.writeBuffer(MysqlChannel.java:467) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.mysql.MysqlChannel.sendOnePacket(MysqlChannel.java:500) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.sendResult(StmtExecutor.java:1747) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.handleQueryStmt(StmtExecutor.java:1674) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.handleQueryWithRetry(StmtExecutor.java:779) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.executeByNereids(StmtExecutor.java:731) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:533) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:512) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.ConnectProcessor.executeQuery(ConnectProcessor.java:307) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.ConnectProcessor.handleQuery(ConnectProcessor.java:203) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.MysqlConnectProcessor.handleQuery(MysqlConnectProcessor.java:177) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.MysqlConnectProcessor.dispatch(MysqlConnectProcessor.java:205) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.MysqlConnectProcessor.processOnce(MysqlConnectProcessor.java:258) ~[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:1149) ~[?:1.8.0_352-352] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_352-352] at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_352-352] ``` After that, if user call `connection.close()` in jdbc, it may be blocked. And we can still see this connection in `show processlist`. We should kill this connection because it is already broken.
dataroaring
pushed a commit
that referenced
this pull request
Jun 21, 2024
…led error (#36559) Some time we met error like: ``` 2024-06-15 17:26:16,492 WARN (mysql-nio-pool-206|11598) [ConnectProcessor.handleQueryException():420] Process one query failed because IOException: java.io.IOException: Write mysql packet failed.[write=646624, needToWrite=2097119] at org.apache.doris.mysql.MysqlChannel.realNetSend(MysqlChannel.java:407) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.mysql.MysqlChannel.flush(MysqlChannel.java:436) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.mysql.MysqlChannel.writeBuffer(MysqlChannel.java:467) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.mysql.MysqlChannel.sendOnePacket(MysqlChannel.java:500) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.sendResult(StmtExecutor.java:1747) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.handleQueryStmt(StmtExecutor.java:1674) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.handleQueryWithRetry(StmtExecutor.java:779) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.executeByNereids(StmtExecutor.java:731) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:533) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:512) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.ConnectProcessor.executeQuery(ConnectProcessor.java:307) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.ConnectProcessor.handleQuery(ConnectProcessor.java:203) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.MysqlConnectProcessor.handleQuery(MysqlConnectProcessor.java:177) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.MysqlConnectProcessor.dispatch(MysqlConnectProcessor.java:205) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.qe.MysqlConnectProcessor.processOnce(MysqlConnectProcessor.java:258) ~[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:1149) ~[?:1.8.0_352-352] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_352-352] at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_352-352] ``` After that, if user call `connection.close()` in jdbc, it may be blocked. And we can still see this connection in `show processlist`. We should kill this connection because it is already broken.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some time we met error like:
After that, if user call
connection.close()in jdbc, it may be blocked.And we can still see this connection in
show processlist.We should kill this connection because it is already broken.