[GitHub] [shardingsphere] dmbj commented on issue #7223: does scaling support resume ?

[GitBox <gi...@apache.org>]

dmbj commented on issue #7223:
URL: https://github.com/apache/shardingsphere/issues/7223#issuecomment-685452592


   here my case for example:
   1.6000w+ data intent to sharding
   2.mysql version 5.6.45-log base VIP mod,binlog `expire_logs_days:7 max_binlog_size:500m`
   3.scaling & proxy version:5.0.0.RC.snapshot
   
   use less then 2 day to sync  INVENTORY_DATA, when INVENTORY_DATA sync finished and begin to sync increase Data, occur exceptions
   ```
   [ERROR] 13:25:47.613 [nioEventLoopGroup-4-1] o.a.s.s.mysql.client.MySQLClient - protocol resolution error
   io.netty.handler.codec.DecoderException: java.lang.RuntimeException: Decode binlog event failed, errorCode: 1236, sqlState: HY000, errorMessage: Could not find first log file name in binary log index file
           at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:468)
           at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
           at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:377)
           at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363)
           at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:355)
           at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:321)
           at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:295)
           at io.netty.handler.codec.ByteToMessageCodec.channelRead(ByteToMessageCodec.java:103)
           at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:377)
           at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363)
           at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:355)
           at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
           at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:377)
           at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363)
           at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
           at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
           at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
           at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
           at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
           at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
           at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
           at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
           at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
           at java.lang.Thread.run(Thread.java:745)
   Caused by: java.lang.RuntimeException: Decode binlog event failed, errorCode: 1236, sqlState: HY000, errorMessage: Could not find first log file name in binary log index file
           at org.apache.shardingsphere.scaling.mysql.client.netty.MySQLBinlogEventPacketDecoder.checkError(MySQLBinlogEventPacketDecoder.java:101)
           at org.apache.shardingsphere.scaling.mysql.client.netty.MySQLBinlogEventPacketDecoder.decode(MySQLBinlogEventPacketDecoder.java:57)
           at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:498)
           at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:437)
           ... 23 common frames omitted
   ```
   then `SHOW BINARY LOGS;` to check binlog filelist, found scaling job target binlog file is not exists.
   now here is the quesion:
   
   does scaling support resume or start increase data from Specify binlog file position?
   so could not restart a new job sync INVENTORY_DATA again
   
   


----------------------------------------------------------------
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