1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
con risposta 2 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 3 anni fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
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?