Re:RE: binlog文件丢失问题

Fri, 19 Jan 2024 01:36:48 -0800 








抱歉,具体报错和代码如下:


报错部分:
Caused by: java.lang.IllegalStateException: The connector is trying to read 
binlog starting at 
Struct{version=1.5.4.Final,connector=mysql,name=mysql_binlog_source,ts_ms=1705645599953,db=,server_id=0,file=mysql_bin.007132,pos=729790304,row=0},
 but this is no longer available on the server. Reconfigure the connector to 
use a snapshot when needed.
at 
com.ververica.cdc.connectors.mysql.debezium.task.context.StatefulTaskContext.loadStartingOffsetState(StatefulTaskContext.java:179)
at 
com.ververica.cdc.connectors.mysql.debezium.task.context.StatefulTaskContext.configure(StatefulTaskContext.java:112)
at 
com.ververica.cdc.connectors.mysql.debezium.reader.BinlogSplitReader.submitSplit(BinlogSplitReader.java:93)
at 
com.ververica.cdc.connectors.mysql.debezium.reader.BinlogSplitReader.submitSplit(BinlogSplitReader.java:65)
at 
com.ververica.cdc.connectors.mysql.source.reader.MySqlSplitReader.checkSplitOrStartNext(MySqlSplitReader.java:170)
at 
com.ververica.cdc.connectors.mysql.source.reader.MySqlSplitReader.fetch(MySqlSplitReader.java:75)
at 
org.apache.flink.connector.base.source.reader.fetcher.FetchTask.run(FetchTask.java:58)
at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:142)
... 6 more




代码部分: 
if (!isBinlogAvailable(mySqlOffsetContext)) {
    throw new IllegalStateException(
            "The connector is trying to read binlog starting at "
                    + mySqlOffsetContext.getSourceInfo()
                    + ", but this is no longer "
                    + "available on the server. Reconfigure the connector to 
use a snapshot when needed.");
}

在 2024-01-19 17:33:03，"Jiabao Sun" <jiabao....@xtransfer.cn.INVALID> 写道：
>Hi,
>
>你的图挂了，可以贴一下图床链接或者直接贴一下代码。
>
>Best,
>Jiabao
>
>
>On 2024/01/19 09:16:55 wyk wrote:
>> 
>> 
>> 各位大佬好:
>>         现在有一个binlog文件丢失问题,需要请教各位,具体问题描述如下:
>> 
>> 
>> 问题描述:
>> 场景: 公司mysql有两个备库: 备库1和备库2。
>> 1. 现在备库1需要下线,需要将任务迁移至备库2
>> 2.我正常将任务保存savepoint后,将链接信息修改为备库2从savepoint启动,这个时候提示报错binlog文件不存在问题,报错截图如下图一
>> 3.我根据报错找到对应代码(如下图二)后,发现是一块校验binlog文件是否存在的逻辑,我理解的是我们从gtid启动不需要对binlog文件进行操作,就将这部分代码进行了注释,任务能够正常从savepoint启动,并且数据接入正常
>> 
>> 
>> 
>> 
>> 疑问: 想问一下校验binlog文件是否存在这块逻辑是否需要,或者是应该修改为校验gtid是否存在,期待您的回复,谢谢
>> 
>> 
>> 注意: 备库一个备库二的gtid是保持一致的
>> 
>> 
>> 
>> 
>> 图一:
>> 
>> 
>> 图二:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 






















					回复