- Newest
- Most votes
- Most comments
Hi! Looking at the docs https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dms_replication_task there is a note which seems relevant:
NOTE: Changing most arguments will stop the task if it is running. You can set start_replication_task to resume the task afterwards.
Unfortunately, the docs don't indicate the type of the parameter so I suggest you look at your state to see if it should be start_replication_task = true
or something else.
Hope this helps!
Whenever you Stop and Resume an AWS DMS task, it resumes from the position where it was paused. Meaning, if you resume the task after X minutes, AWS DMS task will try to get the changes since it was paused by reading the Binary Logs. Looking at the error, it looks like the task was not able to find the required Binary Logs to resume the replication.
If you happen to Stop the DMS task, make sure that the DB host has all the required Binary Logs available so that the task can be successfully resumed.
Ya you are right , I suspect the same too .
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- Why is no data migrated from my Amazon S3 source endpoint even though my AWS DMS task is successful?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
Yes, but I think the pointer to the binary log is getting lost, in which case its unable to resume