Skip to content

Commit ad26964

Browse files
authored
complete upload before starting import (#205)
1 parent 445be30 commit ad26964

File tree

2 files changed

+13
-9
lines changed

2 files changed

+13
-9
lines changed

modules/sideloader/pages/migrate-sideloader.adoc

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -672,7 +672,8 @@ Microsoft Azure::
672672
For example, `/var/lib/cassandra/data/`.
673673
* *`SNAPSHOT_NAME`*: The name of the xref:sideloader:migrate-sideloader.adoc#create-snapshots[snapshot backup] that you created with `nodetool snapshot`.
674674
* *`MIGRATION_DIR`*: The entire `uploadBucketDir` value that was generated when you xref:sideloader:migrate-sideloader.adoc#initialize-migration[initialized the migration], including the trailing slash.
675-
* *`NODE_NAME`*: The host name of the current node you are uploading the snapshot from.
675+
* *`NODE_NAME`*: The host name of the node that your snapshots are from.
676+
It is important to use the specific node name to ensure that each node has a unique directory in the migration bucket.
676677
677678
+
678679
[source,bash,subs="+quotes"]
@@ -720,20 +721,20 @@ After uploading snapshots, you must xref:sideloader:migrate-sideloader.adoc#impo
720721

721722
=== Idle migration directories are evicted
722723

723-
As an added security measure, migrations that remain continuously idle for one week are subject to xref:sideloader:cleanup-sideloader.adoc[automatic cleanup], which deletes all associated snapshots, revokes any unexpired upload credentials, and then closes the migration.
724-
725-
{company} recommends that you xref:sideloader:cleanup-sideloader.adoc#reschedule-a-cleanup[manually reschedule the cleanup] if you don't plan to launch the migration within one week or if you need several days to upload snapshots or import data.
726-
727724
[WARNING]
728725
====
729726
For large migrations, it can take several days to upload snapshots and import data.
730727
Make sure you xref:sideloader:cleanup-sideloader.adoc#reschedule-a-cleanup[manually reschedule the cleanup] to avoid automatic cleanup.
731728
====
732729

730+
As an added security measure, migrations that remain continuously idle for one week are subject to xref:sideloader:cleanup-sideloader.adoc[automatic cleanup], which deletes all associated snapshots, revokes any unexpired upload credentials, and then closes the migration.
731+
732+
{company} recommends that you xref:sideloader:cleanup-sideloader.adoc#reschedule-a-cleanup[manually reschedule the cleanup] if you don't plan to launch the migration within one week or if you need several days to upload snapshots or import data.
733+
733734
[#import-data]
734735
== Import data
735736

736-
After you upload snapshots for each origin node, import the data into your target database.
737+
After you completely upload snapshots for each origin node, import the data into your target database.
737738

738739
Data import is a multi-step operation that requires complete success.
739740
If one step fails, then the entire import operation stops and the migration fails.
@@ -745,10 +746,12 @@ If one step fails, then the entire import operation stops and the migration fail
745746
include::sideloader:partial$sideloader-partials.adoc[tags=import]
746747
======
747748

748-
[TIP]
749+
[WARNING]
749750
====
750-
If necessary, you can xref:sideloader:stop-restart-sideloader.adoc[pause or abort the migration] during the import process.
751+
* Before you start the import process, make sure all snapshots are completely uploaded.
752+
For commands to monitor upload progress and compare uploaded data against the original snapshots, see xref:sideloader:migrate-sideloader.adoc#upload-snapshots-to-migration-directory[Upload snapshots to the migration directory].
751753
754+
* If necessary, you can xref:sideloader:stop-restart-sideloader.adoc[pause or abort the migration] during the import process.
752755
include::sideloader:partial$sideloader-partials.adoc[tags=no-return]
753756
====
754757

modules/sideloader/partials/sideloader-partials.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,8 @@ For example, `/var/lib/cassandra/data`.
1818
* *`KEYSPACE_NAME`*: The name of the keyspace that contains the tables you want to migrate.
1919
* *`SNAPSHOT_NAME`*: The name of the xref:sideloader:migrate-sideloader.adoc#create-snapshots[snapshot backup] that you created with `nodetool snapshot`.
2020
* *`MIGRATION_DIR`*: The entire `uploadBucketDir` value that was generated when you xref:sideloader:migrate-sideloader.adoc#initialize-migration[initialized the migration], including the trailing slash.
21-
* *`NODE_NAME`*: The host name of the current node you are uploading the snapshot from.
21+
* *`NODE_NAME`*: The host name of the node that your snapshots are from.
22+
It is important to use the specific node name to ensure that each node has a unique directory in the migration bucket.
2223
// end::command-placeholders-common[]
2324
2425
// tag::validate[]

0 commit comments

Comments
 (0)