-
Notifications
You must be signed in to change notification settings - Fork 500
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
Update MA getting started #8797
Conversation
Signed-off-by: Archer <[email protected]>
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
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.
Thanks for making these changes. Overall looks great, I've weight in mostly around refining the 'technical' details.
I've made a couple of comments with [Editorial] where I suspect you'll have a better sense of any rewriting if needed.
Co-authored-by: Peter Nied <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Co-authored-by: Peter Nied <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
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.
@Naarcha-AWS Please see my comments and changes and let me know if you have any questions. Thanks!
Before utilizing this quickstart, make sure you fulfill the following prerequisites: | ||
|
||
* Verify your that migration path [is supported](https://opensearch.org/docs/latest/migrations/is-migration-assistant-right-for-you/#supported-migration-paths). Note that we test with the exact versions specified, but you should be able to migrate data on alternative minor versions as long as the major version is supported. | ||
* The source cluster must be deployed with the S3 plugin. |
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.
Is this the actual name of the plugin, or should it be "Amazon S3 plugin" or "Amazon Simple Storage Service (Amazon S3) plugin"? In other words, ensure that we use the actual name of the plugin.
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.
Lets use the name.
Shards unclaimed: 5 | ||
``` | ||
|
||
Logs and metrics are available in CloudWatch under the `OpenSearchMigrations` log 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.
Logs and metrics are available in CloudWatch under the `OpenSearchMigrations` log group. | |
Logs and metrics are available in Amazon CloudWatch in the `OpenSearchMigrations` log group. |
|
||
--- | ||
|
||
## Step 12: Verify all documents were migrated |
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.
## Step 12: Verify all documents were migrated | |
## Step 12: Verify that all documents were migrated |
|
||
## Step 12: Verify all documents were migrated | ||
|
||
Use the following query in CloudWatch logs insights to identify failed documents: |
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.
Use the following query in CloudWatch logs insights to identify failed documents: | |
Use the following query in CloudWatch Logs Insights to identify failed documents: |
| limit 10000 | ||
``` | ||
|
||
If any failed documents are identified, you can index the failed documents directly, as opposed to using RFS. |
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.
If any failed documents are identified, you can index the failed documents directly, as opposed to using RFS. | |
If any failed documents are identified, you can index the failed documents directly as opposed to using RFS. |
|
||
If any failed documents are identified, you can index the failed documents directly, as opposed to using RFS. | ||
|
||
For more information, see [Backfill migration]. |
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.
Add link
|
||
These commands deploy the following stacks: | ||
|
||
* Migration assistant network stack |
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.
* Migration assistant network stack | |
* Migration Assistant network stack |
console backfill start | ||
``` | ||
|
||
2. _(Optional)_ To speed up the migration, increase the number of documents processed at a time by using the following command: |
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.
2. _(Optional)_ To speed up the migration, increase the number of documents processed at a time by using the following command: | |
2. _(Optional)_ To speed up the migration, increase the number of documents processed at a simultaneously by using the following command: |
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Edits the Migration assistant getting started page. This PR makes the following modifications:
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.