From 658923e5862b52b5c678c03c3955027a685d50c2 Mon Sep 17 00:00:00 2001 From: Arunprasad Rajkumar Date: Thu, 7 Nov 2024 14:13:07 +0530 Subject: [PATCH] Add resource recommendation for EC2 instance used in live-migration (#3561) Signed-off-by: Arunprasad Rajkumar --- _partials/_migrate_live_migrate_faq_all.md | 9 +++++++++ _partials/_migrate_prerequisites.md | 1 + migrate/live-migration.md | 1 + 3 files changed, 11 insertions(+) diff --git a/_partials/_migrate_live_migrate_faq_all.md b/_partials/_migrate_live_migrate_faq_all.md index cde56051c6..60afd8dab5 100644 --- a/_partials/_migrate_live_migrate_faq_all.md +++ b/_partials/_migrate_live_migrate_faq_all.md @@ -1,3 +1,5 @@ +import CleanupData from "versionContent/_partials/_migrate_live_migration_cleanup.mdx"; + ### ERROR: relation "xxx.yy" does not exist This may happen when a relation is removed after executing the `snapshot` command. A relation can be @@ -36,6 +38,13 @@ To resolve this issue: 1. When `migrate` has finished, manually refresh the materialized views you excluded. +### Inactive or lagging replication slots + +If you encounter an “Inactive or lagging replication slots” warning on your cloud provider console after using live-migration, it might be due to lingering replication slots created by the live-migration tool on your source database. + + + + ### Role passwords Because of issues dumping passwords from various managed service providers, Live-migration diff --git a/_partials/_migrate_prerequisites.md b/_partials/_migrate_prerequisites.md index e0d149d649..ccb8d3e880 100644 --- a/_partials/_migrate_prerequisites.md +++ b/_partials/_migrate_prerequisites.md @@ -10,6 +10,7 @@ Before you migrate your data: Each Timescale Cloud service [has a single database] that supports the [most popular extensions][all available extensions]. Timescale Cloud services do not support [tablespaces], and [there is no superuser associated with a Timescale service][no-superuser-for-timescale-instance]. + We recommend creating a Timescale Cloud instance with at least 8 CPUs for a smoother migration experience. A higher-spec instance can significantly reduce the overall migration window. - To ensure that maintenance does not run while migration is in progress, best practice is to [adjust the maintenance window][adjust-maintenance-window]. diff --git a/migrate/live-migration.md b/migrate/live-migration.md index 619014eb46..571ec96a6e 100644 --- a/migrate/live-migration.md +++ b/migrate/live-migration.md @@ -52,6 +52,7 @@ the live-migration Docker image. This machine needs sufficient space to store the buffered changes that occur while your data is being copied. This space is proportional to the amount of new uncompressed data being written to the Timescale Cloud service during migration. A general rule of thumb is between 100GB and 500GB. + The CPU specifications of this EC2 instance should match those of your Timescale Cloud instance for optimal performance. For example, if your Timescale Cloud instance has an 8-CPU configuration, then your EC2 instance should also have 8 CPUs. - Before starting live-migration, read the [Frequently Asked Questions][FAQ].