You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/05/15 02:47:43 UTC
[GitHub] [shardingsphere] henrypoter commented on issue #5598: sharding-proxy process disappear without any error log
henrypoter commented on issue #5598:
URL: https://github.com/apache/shardingsphere/issues/5598#issuecomment-628994981
### I tried again.
### proxy log
`[INFO ] 23:26:26.254 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ: [id: 0x9ab2eaed, L:/127.0.0.1:3307 - R:/127.0.0.1:44824]
[INFO ] 23:26:26.254 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ COMPLETE
[INFO ] 23:26:35.216 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ: [id: 0xc459e4a7, L:/127.0.0.1:3307 - R:/127.0.0.1:44828]
[INFO ] 23:26:35.217 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ COMPLETE
[INFO ] 23:26:40.130 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ: [id: 0x732b2d12, L:/127.0.0.1:3307 - R:/127.0.0.1:44830]
[INFO ] 23:26:40.130 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ COMPLETE
[WARN ] 23:26:40.169 [epollEventLoopGroup-3-6] i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
[INFO ] 23:26:42.615 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ: [id: 0x7f6810a3, L:/127.0.0.1:3307 - R:/127.0.0.1:44836]
[INFO ] 23:26:42.615 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ COMPLETE
[WARN ] 23:26:56.954 [epollEventLoopGroup-3-7] i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
[INFO ] 23:26:57.077 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ: [id: 0xd5a1cdf5, L:/127.0.0.1:3307 - R:/127.0.0.1:44842]
[INFO ] 23:26:57.078 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ COMPLETE
[INFO ] 23:27:31.375 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ: [id: 0x33b6efbd, L:/127.0.0.1:3307 - R:/127.0.0.1:44848]
[INFO ] 23:27:31.376 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ COMPLETE
[INFO ] 23:35:45.624 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ: [id: 0x190bdd95, L:/127.0.0.1:3307 - R:/127.0.0.1:44852]
[INFO ] 23:35:45.625 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xa3539356, L:/0.0.0.0:3307] READ COMPLETE
line 1:0 no viable alternative at input 'KILL'
line 1:0 mismatched input 'KILL' expecting {SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, TRUNCATE, GRANT, REVOKE, SET, WITH, DESC, BEGIN, COMMIT, ROLLBACK, SAVEPOINT, CALL, USE, DESCRIBE, SHOW, REPLACE, START, CHANGE, RENAME, REPAIR, STOP}
[ERROR] 23:35:45.687 [ShardingSphere-Command-13] o.a.s.s.f.c.CommandExecutorTask - Exception occur:
org.apache.shardingsphere.sql.parser.exception.SQLParsingException: Unsupported SQL of `KILL QUERY 121`
at org.apache.shardingsphere.sql.parser.core.parser.SQLParserExecutor.execute(SQLParserExecutor.java:49)
at org.apache.shardingsphere.sql.parser.SQLParserEngine.parse0(SQLParserEngine.java:79)
at org.apache.shardingsphere.sql.parser.SQLParserEngine.parse(SQLParserEngine.java:61)
at org.apache.shardingsphere.shardingproxy.backend.text.TextProtocolBackendHandlerFactory.newInstance(TextProtocolBackendHandlerFactory.java:69)
at org.apache.shardingsphere.shardingproxy.frontend.mysql.command.query.text.query.MySQLComQueryPacketExecutor.<init>(MySQLComQueryPacketExecutor.java:65)
at org.apache.shardingsphere.shardingproxy.frontend.mysql.command.MySQLCommandExecutorFactory.newInstance(MySQLCommandExecutorFactory.java:70)
at org.apache.shardingsphere.shardingproxy.frontend.mysql.command.MySQLCommandExecuteEngine.getCommandExecutor(MySQLCommandExecuteEngine.java:59)
at org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.executeCommand(CommandExecutorTask.java:92)
at org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.run(CommandExecutorTask.java:71)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[WARN ] 23:35:57.145 [epollEventLoopGroup-3-2] i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
`
### scaling log
`[INFO ] 19:09:47.529 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0x2fa1461d, L:/192.168.11.182:8888 - R:/192.168.11.123:63056]
[INFO ] 19:09:47.530 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
[INFO ] 19:09:47.530 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0x8036331a, L:/192.168.11.182:8888 - R:/192.168.11.123:63057]
[INFO ] 19:09:47.531 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
[ERROR] 23:35:56.980 [pool-1-thread-10] o.a.s.s.c.e.e.SyncTaskExecuteCallback - HistoryDataSyncTask history-biz_suite-t_suite_scheduling_time#0 execute exception exit
org.apache.shardingsphere.shardingscaling.core.exception.SyncTaskExecuteException: java.sql.SQLException: 2Unknown exception: [Unsupported SQL of `KILL QUERY 121`]
at org.apache.shardingsphere.shardingscaling.core.execute.executor.writer.AbstractJDBCWriter.write(AbstractJDBCWriter.java:90)
at org.apache.shardingsphere.shardingscaling.core.execute.executor.writer.AbstractJDBCWriter.run(AbstractJDBCWriter.java:72)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLException: 2Unknown exception: [Unsupported SQL of `KILL QUERY 121`]
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:965)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3978)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3914)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2530)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2683)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2491)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2449)
at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:845)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:745)
at com.mysql.jdbc.StatementImpl$CancelTask$1.run(StatementImpl.java:120)
[INFO ] 23:35:57.012 [pool-1-thread-10] o.a.s.s.c.c.task.SyncTaskController - history data migrate task historyGroup-biz_suite finished, execute result: EXCEPTION_EXIT
[INFO ] 23:35:57.037 [pool-1-thread-10] com.zaxxer.hikari.HikariDataSource - HikariPool-5 - Shutdown initiated...
[INFO ] 23:35:57.161 [pool-1-thread-10] com.zaxxer.hikari.HikariDataSource - HikariPool-5 - Shutdown completed.
[INFO ] 23:35:57.162 [pool-1-thread-10] com.zaxxer.hikari.HikariDataSource - HikariPool-4 - Shutdown initiated...
[INFO ] 23:35:57.177 [pool-1-thread-10] com.zaxxer.hikari.HikariDataSource - HikariPool-4 - Shutdown completed.
[INFO ] 23:35:57.177 [pool-1-thread-10] com.zaxxer.hikari.HikariDataSource - HikariPool-3 - Shutdown initiated...
[INFO ] 23:35:57.189 [pool-1-thread-10] com.zaxxer.hikari.HikariDataSource - HikariPool-3 - Shutdown completed.
[ERROR] 23:35:57.284 [pool-1-thread-16] o.a.s.s.c.e.e.SyncTaskExecuteCallback - HistoryDataSyncTask history-biz_suite-t_suite_scheduling_time#3 execute exception exit
java.lang.NullPointerException: null
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2513)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1903)
at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:1242)
at com.zaxxer.hikari.pool.ProxyPreparedStatement.execute(ProxyPreparedStatement.java:44)
at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.execute(HikariProxyPreparedStatement.java)
at org.apache.shardingsphere.shardingscaling.core.execute.executor.writer.AbstractJDBCWriter.executeInsert(AbstractJDBCWriter.java:128)
at org.apache.shardingsphere.shardingscaling.core.execute.executor.writer.AbstractJDBCWriter.flush(AbstractJDBCWriter.java:103)
at org.apache.shardingsphere.shardingscaling.core.execute.executor.writer.AbstractJDBCWriter.write(AbstractJDBCWriter.java:81)
at org.apache.shardingsphere.shardingscaling.core.execute.executor.writer.AbstractJDBCWriter.run(AbstractJDBCWriter.java:72)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[INFO ] 23:35:57.285 [pool-1-thread-16] o.a.s.s.c.c.task.SyncTaskController - history data migrate task historyGroup-biz_suite finished, execute result: EXCEPTION_EXIT
[INFO ] 09:29:35.556 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0x32c6485e, L:/192.168.11.182:8888 - R:/192.168.11.123:58203]
[INFO ] 09:29:35.634 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
[INFO ] 09:29:35.635 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0x8bc55de3, L:/192.168.11.182:8888 - R:/192.168.11.123:58202]
[INFO ] 09:29:35.636 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
[INFO ] 09:29:35.637 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0x19caddaa, L:/192.168.11.182:8888 - R:/192.168.11.123:58204]
[INFO ] 09:29:35.637 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
[INFO ] 09:29:45.892 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0x70ac6510, L:/192.168.11.182:8888 - R:/192.168.11.123:58232]
[INFO ] 09:29:45.903 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
[INFO ] 10:41:47.554 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0xfee6faa3, L:/192.168.11.182:8888 - R:/192.168.11.123:55039]
[INFO ] 10:41:47.555 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
[INFO ] 10:41:47.555 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ: [id: 0x9f2edf2a, L:/192.168.11.182:8888 - R:/192.168.11.123:55040]
[INFO ] 10:41:47.556 [nioEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc26b991c, L:/0.0.0.0:8888] READ COMPLETE
`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org