Add resource recommendation for EC2 instance used in live-migration (#…

…3561) Signed-off-by: Arunprasad Rajkumar <[email protected]>
timescale · Nov 7, 2024 · 658923e · 658923e
1 parent 9590e09
commit 658923e
Show file tree

Hide file tree

Showing 3 changed files with 11 additions and 0 deletions.
diff --git 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.
+
+<CleanupData />
+
+
 ### 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
@@ -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
@@ -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].