我们现在有一个mongoDB-cdc的任务一天前失败了,但是没有报警,所以今天才发现,但是想要从checkpoint重启时报下面的错误,看样子应该是resumeToken失效的缘故。请问下,这种情况是不是只能依靠监控来及时的趁resumeToken还没失效就赶紧修复并恢复任务?还有别的方式么?Caused by: com.mongodb.MongoCommandException: Command failed with error 286 (ChangeStreamHistoryLost): 'Resume of change stream was not possible, as the resume point may no longer be in the oplog.' on server 192.168.0.202:3717. The full response is {"errorLabels": ["NonResumableChangeStreamError"], "operationTime": {"$timestamp": {"t": 1666087462, "i": 46}}, "ok": 0.0, "errmsg": "Resume of change stream was not possible, as the resume point may no longer be in the oplog.", "code": 286, "codeName": "ChangeStreamHistoryLost", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1666087462, "i": 46}}, "signature": {"hash": {"$binary": {"base64": "KgLy18PJF1vX/OcP8UMErIXSpj4=", "subType": "00"}}, "keyId": 7125022634332389401}}} at com.mongodb.internal.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:195)
版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。
实时计算Flink版是阿里云提供的全托管Serverless Flink云服务,基于 Apache Flink 构建的企业级、高性能实时大数据处理系统。提供全托管版 Flink 集群和引擎,提高作业开发运维效率。