You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-src/zdm-core/modules/migrate/pages/deployment-infrastructure.adoc
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,15 @@ We will use the term "machine" to indicate a cloud instance (on any cloud provid
51
51
52
52
[NOTE]
53
53
====
54
-
Scenario: when you have close to 12 TBs of data and several tables, to speed up the migration of your existing data, you can run with (for example) 4 machines that are the equivalent of an AWS `m5.4xlarge`, a GCP `e2-standard-16` or an Azure `D16v5`. Then run {dsbulk-migrator} on each machine, with each one responsible for a quarter of the full token range.
54
+
* Scenario: If you have 20 TBs of existing data to be migrated and want to speed up the migration, you could use multiple VMs. For example, you can use four VMs that are the equivalent of an AWS m5.4xlarge, a GCP e2-standard-16 or an Azure D16v5.
55
+
+
56
+
Next, run DSBulk Migrator or Cassandra-Data-Migrator in parallel on each VM with each one responsible for migrating around 5TB of data. If there is one super large table (e.g. 15 TB of 20 TB is in one table), you can choose to migrate this table in three parts on three separate VMs in parallel by splitting the full token range into three parts and migrating the rest of the tables on the fourth VM.
57
+
58
+
* Ensure that your Origin and Target clusters can handle high traffic from Cassandra Data Migrator or DSBulk in addition to the live traffic from your application.
59
+
60
+
* Test any migration in a lower environment before you plan to do it in production.
61
+
62
+
* Contact https://support.datastax.com/s/[DataStax support] for help configuring your workload.
55
63
====
56
64
57
65
// TODO: investigate how to "leverage the parallelism of {cstar-data-migrator} to run the migration process across all 4 machines."
0 commit comments