AWS DMS 从 MySQL 更改数据捕获
我设置了“full-load-and-cdc”迁移任务来跟踪 MySQL 数据库中所做的更改并将更改复制到 AWS S3。该集群是 InnoDB，我连接到其中一个副本。有时，实例必须从集群中分离，然后作为克隆添加回来。在这种情况下，所有复制任务都会失败，并出现如下错误：“无法在二进制日志索引文件中找到第一个日志文件名”。
所以，看起来具有特定名称的 BinLog 文件不再存在。在这种情况下我可以做什么并确保从上一个检查点继续复制？
I have "full-load-and-cdc" migrations tasks set up to track changes made in MySQL database and replicate changes to AWS S3. The cluster is InnoDB and I connect to one of the replicas. Sometimes, it happens that instance has to be detached from cluster and then added back as clone. In this situation all replication tasks fail with errors like this: "Could not find first log file name in binary log index file".
So, it looks like BinLog file with a specific name doesn't exist anymore. What could I do in a situation like this and be sure I continue replication from last checkpoint?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论