-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC-4238, DOC-4510 Sideloader GA prep, Relaunch function, begin migration docs cleanup #194
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
submitting my comments so far
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
This comment was marked as resolved.
This comment was marked as resolved.
Build successful! ✅
Deploying draft. |
-- | ||
Because {sstable-sideloader} operations are typically short-term, resource-intensive events, you can create a flexible capacity PCU group exclusively to support your target database during the migration. | ||
|
||
//After PCU PR merge: xref:astra-db-serverless:administration:create-pcu.adoc#flexible-capacity[create a flexible capacity PCU group] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edit link before merge (1)
-- | ||
If you plan to keep your target database in a PCU group after the migration, you can create a committed capacity PCU group for your target database. | ||
|
||
//After PCU PR merge: xref:astra-db-serverless:administration:create-pcu.adoc#committed-capacity[create a committed capacity PCU group] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edit link before merge (2)
Build successful! ✅
Deploying draft. |
1 similar comment
Build successful! ✅
Deploying draft. |
Build successful! ✅
Deploying draft. |
== Command line knowledge requirements | ||
|
||
Due to the nature of the {sstable-sideloader} process and the tools involved, you need to be familiar with using the command line, including the following: | ||
|
||
* Installing and using CLI tools | ||
* Issuing curl commands | ||
* Basic scripting | ||
* Modifying example command to your environment | ||
* Security best practices | ||
|
||
[IMPORTANT] | ||
==== | ||
The {sstable-sideloader} process uses authentication credentials to write to the migration directory and your database. | ||
|
||
Make sure you understand how to securely store and use sensitive credentials when working on the command line. | ||
==== |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eric suggested moving this to the top of the page
Direct changes for Sideloader GA
Prepare for Sideloader GA (DOC-4238):
General migration doc cleanup
Begin general cleanup of the migration docs:
includes
the entire body of cassandra-data-migrator.adoc.ifdef
and{imageprefix}
The following pages will receive further edits in future PRs. They don't need a detailed review at this time:
This PR is dependent on: