For more information about CPU credits and baseline performance, see CPU Credits and Baseline Performance for Burstable Performance Instances.Īfter you identify the source of the silent failure, restart the task. For this reason, take into account the instance type that is used and verify the CPU utilization accordingly. For example, a T2.micro instance provides a baseline performance of 10%. Note: T2 instances provide a baseline performance after the CPU credits are exhausted. Or, consider scaling up the replication instance to a larger instance type. You can do this by launching new replication instances and distributing the tasks across multiple replication instances. If you see constant CPU or memory contention, consider reducing the number of tasks that are running on the replication instance. This opens the CloudWatch console where you can view the metric's utilization at the time that the task failed.
In the Migration task metrics section, you can view the CPUUtilization, SwapUsage, FreeableMemory, and FreeStorageSpace metrics.Choose the name of the replication instance noted in the step 3.
Choose Replication instances from the navigation pane.Note the name of the Replication instance from the Overview details section.Open the AWS DMS console, and choose Database migration tasks from the navigation pane.To view the CloudWatch metrics, follow these steps: For more information, see Data Migration Service metrics. If you see a combination of the low FreeableMemory and high SwapUsage, then there might be memory contention on the replication instance. Then, verify the CPU, memory, and disk utilization on the replication instance around the same time that the failure was logged. First, check the time of the last entry in the task logs after the task failed silently.
0 kommentar(er)
