- Newest
- Most votes
- Most comments
Sorry I did not specify this, but yes I am using the new Homegeneous Data Migration service with Full Load and change data capture (CDC). I ran another migration test this morning and received the same results.
I am seeing that the Migration Process is Completed, but I also see a Load running message. So I assume this would be the CDC process taking over.
TL;DR Based on the provided log output: data is continuing to be read and stored in an intermediate location but not yet loaded; no indication of data migration being paused / stopped / terminated.
From Migrating data from MySQL databases with homogeneous data migrations in AWS DMS
For homogeneous data migrations of the Full load and change data capture (CDC) type, AWS DMS uses mydumper to read data from your source database and store it on the disk attached to the serverless environment. After AWS DMS reads all your source data, it uses myloader in the target database to restore your data. After AWS DMS completes the full load, it sets up the binlog replication with the binlog position set to the start of the full load."
Source database network transmit throughput, read IOPS etc. metrics while migrating a RDS MySQL DB (several hundred gigabytes) using Homogeneous Data Migration corroborate the above. Migration of a relatively smaller MySQL database displayed a similar set of CloudWatch log messages and completed successfully.
The status of the migration can be viewed by navigating to DMS -> Migration Projects -> Data migrations and also by clicking on the link associated with the data migration and then viewing the metrics under the Monitoring tab.
Related docs:
Notes:
- OP appears to be using the recently introduced Homegeneous Data Migration capabilities in DMS and not the "traditional" DMS (endpoints, replication instances, migration tasks).
- This is a revised / updated answer based on new observations since my earlier answer (which was heavily biased towards traditional DMS). The prior answer has been since deleted but contents of the same are appended FWIW.
Deleted answer:
Provided I am understanding your question correctly, navigating to Database migratiorstasks-> Table Statistics within the DMS service in AWS management console might help answer your questions by providina information on status of table loading (including whether table load errored out).
Here is a related re:Post Knowledge Center article: How do I use table statistics to monitor an AWS DMS task?.
Curious as to where / how in CloudWatch you are able to view the estimated row counts etc.? This appears to have some additional detail bevond what is available in Table Statistics.
Hope that helps.
Relevant content
- asked 2 years ago
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
TL;DR My migrations are taking a while likely due to large size of DBs and small target instance size; based on viewing metrics, processes and row counts on target RDS instance, the migration is continuing and not stalled
NP. That sounds like it. Thanks for the updates.
My migrations are still running. I used small target instance size for proof-of-concept purposes so that likely is contributing to the slowness.
Some observations: