Remove unnecessary live-migration config recommendations (#3655)

These are now handled by the tool automatically. Signed-off-by: Arunprasad Rajkumar <[email protected]> Co-authored-by: Iain Cox <[email protected]>
timescale · Dec 16, 2024 · 88dc71f · 88dc71f
1 parent 08d3728
commit 88dc71f
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 36 deletions.
diff --git a/_partials/_migrate_live_migrate_faq_all.md b/_partials/_migrate_live_migrate_faq_all.md
@@ -110,27 +110,4 @@ One of the following can be used to avoid the OOM errors:
 
 By taking these steps, you can prevent OOM errors and ensure a smoother migration experience with TimescaleDB.
 
-### ERROR:  invalid snapshot identifier: "xxxxxx" (or) SSL SYSCALL error: EOF detected on RDS
-
-This rare phenomenon may happen when:
-
-- The snapshot becomes stale due to network connection interruption between the snapshot process and your source database.
-
-  When you see you this error you need to tune the tcp parameter tuning on your source RDS instance. Update the
-  following GUCs to the recommended values on the source RDS instance.
-
-   ```shell
-   psql -X -d $SOURCE -c "alter system set tcp_keepalives_count=60"
-   psql -X -d $SOURCE -c "alter system set tcp_keepalives_idle=10"
-   psql -X -d $SOURCE -c "alter system set tcp_keepalives_interval=10"
-   psql -X -d $SOURCE -c "alter system set wal_sender_timeout='30min'"
-   ```
-
-  For more information, see [https://github.com/dimitri/pgcopydb/issues/773#issuecomment-2139093365](https://github.com/dimitri/pgcopydb/issues/773#issuecomment-2139093365)
-
-- Either your source database or target Timescale Cloud service is under CPU/Memory/Disk/Network pressure:
-
-  Upgrade to better instances types until migration completes.
-
-
 [align-versions]: /migrate/:currentVersion:/live-migration/#align-the-version-of-timescaledb-on-the-source-and-target
diff --git a/_partials/_migrate_live_tune_source_database.md b/_partials/_migrate_live_tune_source_database.md
@@ -16,14 +16,6 @@ a managed service, follow the instructions in the `From MST` tab on this page.
    If this command throws an error, [install wal2json][install-wal2json] on
    your source database.
 
-1. **Tune system messaging**
-   ```shell
-   psql -X -d $SOURCE -c "alter system set tcp_keepalives_count=60"
-   psql -X -d $SOURCE -c "alter system set tcp_keepalives_idle=10"
-   psql -X -d $SOURCE -c "alter system set tcp_keepalives_interval=10"
-   psql -X -d $SOURCE -c "alter system set wal_sender_timeout='30min'"
-   ```
-
 1. **Restart the source database** 
 
    Your configuration changes are now active. However, verify that the

diff --git a/_partials/_migrate_live_tune_source_database_awsrds.md b/_partials/_migrate_live_tune_source_database_awsrds.md
@@ -22,11 +22,6 @@ Updating parameters on a PostgreSQL instance will cause an outage. Choose a time
    1. Update the following parameters, then click `Save changes`.
       - `old_snapshot_threshold` set to `-1`: prevent PostgreSQL from treating the data in a snapshot as outdated.
       - `rds.logical_replication` set to `1`: record the information needed for logical decoding.
-      - `tcp_keepalives_count` set to `60`:  the number of messages that can be lost before the client is considered dead.
-      - `tcp_keepalives_idle` set to `10`: the amount of time with no network activity before the IS sends a TCP keepalive message to the client.
-      - `tcp_keepalives_interval` set to `10`: the amount of time before a unacknowledged TCP keepalive message is restransmitted. 
-      - `wal_sender_timeout` set to `30min`: the maximum time to wait for WAL replication.
-
 
    1. In RDS, navigate back to your [databases][databases], select the RDS instance to migrate and click `Modify`.