1 Answer
0
Above error basically means the last oplog position when the dms task was stopped is no longer and there are chances of data loss due to missing transactions. I would suggest increasing the oplog so that the required entry postion is not overwritten
answered 6 months ago
Relevant questions
Does the Amazon Redshift pause and resume functionality also work with DS2 clusters?
Accepted Answerasked 3 years agoDMS and Terraform
asked 14 days agoHow to recover from invalid resume token on DMS MongoDB connector?
asked 6 months agoDMS task stuck in starting for hours
asked 2 years agoDMS 3.4.7 Fails on some tables upload to Redshift : Access denied to KMS key
asked 3 months agoDMS: How does a replication task handle duplicate data w/o Primary/Unique keys on the table
asked 4 months agoDMS Restart removes the delete markers. - how to handle in GLUE
asked 14 days agoDMS Migration MongoDB source and RDS Postgres as destination
Accepted Answerasked 4 months agoConnecting DMS to our local source endpoint
asked 4 months agoDMS replication
asked 2 months ago
How can I recover after the problem has already happened withou deleting the task? Our main issue is because our task are created with terraform. We need to open a PR to fix this issue by recreating the resource because actions available on the UI won't recover from the error. Kafka mongo connector has an entire topic on how to recover from the error but I couldn't find anything similar for Mongo DMS.
https://www.mongodb.com/docs/kafka-connector/current/troubleshooting/recover-from-invalid-resume-token/
It looks like DMS never updates the "Change data capture (CDC) recovery checkpoint". We are unable to keep all the history in the oplog forever. How can we change the CDC to update the recovery checkpoint or restart it programatically?