How to recover from invalid resume token on DMS MongoDB connector?
When we pause our mongo connections on DMS for some hours and the resume point is no longer in the oplog we are unable to restart or resume our task.
Is there any way we can ignore these errors and continue replication or setup a hearbeat similar to Postgres RDS endpoint to update the resume point? The only fix we found was deleting the task and recreating it.
Resume of change stream was not possible, as the resume point may no longer be in the oplog
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
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.
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?
AWS DMS performance degradation until stopped and resumedasked 2 months ago
DMS latencyAccepted Answerasked 3 years ago
DMS task stuck in starting for hoursasked a year ago
How to recover from invalid resume token on DMS MongoDB connector?asked 2 months ago
DMS Controlling the number of source database connections usedasked 8 months ago
DMS to migrate SQL Server from RDS to EC2asked 2 years ago
Does the Amazon Redshift pause and resume functionality also work with DS2 clusters?Accepted Answerasked 2 years ago
DMS instance sizing guidanceAccepted Answerasked 2 years ago
Can we export the mongodb using the data pipeline?Accepted Answerasked 6 years ago
Oracle Migration from on-premises using DMS and RmanAccepted Answerasked 2 years ago