- Más nuevo
- Más votos
- Más comentarios
Absolutely! DMS can run multiple tasks in parallel on the same replication instance, each replication task is its own process. For MySQL, another possible reason why you’re facing issues is because they’re hitting limitations. I highly recommend going over this list as it can cause tasks to fail.
-
Using a MySQL-compatible database as a source for AWS DMS - Limitations on using a MySQL database as a source for AWS DMS - https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MySQL.html#CHAP_Source.MySQL.Limitations
-
Modifying Resource Allocation - Stop all currently running replication tasks, navigate to the AWS DMS console, try increasing size of instances by choosing a larger instance type. https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.Replication.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.Modifying.html#
-
Verify Network Connectivity via Security Group and NACLs - Make sure your target and source databases are accessible and that their corresponding ports are open. Check for any firewall rules or network configs blocking connectivity between the DMS replication instance and the databases. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.VPC.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.html
-
Task Configuration Settings - Double check your task configuration settings for both replication tasks, make sure your target and source endpoints, table mappings, and migration settings are properly configured. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.Creating.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Monitoring.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.html
-
Monitoring - Monitor your replication instance’s resource utilization whenever it’s executing its task. Navigate to the AWS DMS console, open replication instances and select desired replication instance and click on the “Monitoring” tab to view metrics that’s related to memory, CPU, network usage (Cloudwatch Metrics) https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Monitoring.html https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html
-
Restart/Retry - For the replication tasks that fail try restarting them after modifying any configuration rules. Navigate to the AWS DMS console, click “Tasks”, select your task and choose to either “Resume” or “Retry” based on the error
Contenido relevante
- OFICIAL DE AWSActualizada hace 4 años
- OFICIAL DE AWSActualizada hace un mes
- OFICIAL DE AWSActualizada hace 2 años