-
Notifications
You must be signed in to change notification settings - Fork 159
Adds Migrate Elasticsearch with minimal downtime page #2533
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
Adds Migrate Elasticsearch with minimal downtime page #2533
Conversation
🔍 Preview links for changed docs |
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.
Looks great, and thank you for opening the PR! :)
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
…s-with-minimal-downtime.md Co-authored-by: Visha Angelova <[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.
mostly comments around adding interlinking and appropriately contextualizing this doc in the larger docs set
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.
this approach needs to be introduced and compared on the parent page (from https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2533/manage-data/migrate#ec-restore-snapshots) - what is the relationship between this page and the core procedure?
probably also needs an x-link from some key spots in https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2533/deploy-manage/tools/snapshot-and-restore, e.g. https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2533/deploy-manage/tools/snapshot-and-restore/restore-snapshot#restore-entire-cluster + https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2533/deploy-manage/tools/snapshot-and-restore/restore-snapshot#restore-different-cluster
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.
I added a reference in the parent page: KOTungseth@2ee8c59
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Show resolved
Hide resolved
@@ -0,0 +1,77 @@ | |||
--- | |||
navigation_title: Migrate Elasticsearch data with minimal downtime |
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.
because this is in the migration section, we could try:
navigation_title: Migrate Elasticsearch data with minimal downtime | |
navigation_title: Minimize downtime with incremental snapshots |
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.
@shainaraskas I think the goal of this article is to provide an answer to all our customers asking for "zero-downtime" migrations. Incremental snapshots are the technology enabling it, not the end goal. I am totally ok with changing the title but I would like to keep the "downtime" part in there :)
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.
I did a keyword search, and to optimize this page for SEO, we need to keep Elasticsearch
in the title.
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.
this is the nav title, not the page title, so we could simplify this so it's easier to read in the sidebar.
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.
Got it! I think for the nav title @shainaraskas's suggestion makes sense as we are already under the "migrate" section.
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
* **Custom integrations** – Some custom integrations that directly use the {{es}} API can require additional handling during the cutover from the old cluster to the new cluster. | ||
* **Resource usage** – Initial and incremental snapshot and restore operations can be resource-intensive, potentially affecting cluster performance. | ||
|
||
## Additional topics [additional-incremental-snapshot-topics] |
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.
consider integrating most of these into the body.
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md
Outdated
Show resolved
Hide resolved
…s-with-minimal-downtime.md Co-authored-by: shainaraskas <[email protected]>
…s-with-minimal-downtime.md Co-authored-by: shainaraskas <[email protected]>
…s-with-minimal-downtime.md Co-authored-by: shainaraskas <[email protected]>
…s-with-minimal-downtime.md Co-authored-by: Visha Angelova <[email protected]>
…s-with-minimal-downtime.md Co-authored-by: Visha Angelova <[email protected]>
…s-with-minimal-downtime.md Co-authored-by: shainaraskas <[email protected]>
…s-with-minimal-downtime.md Co-authored-by: shainaraskas <[email protected]>
Adds content from the How to migrate Elasticsearch clusters with zero downtime blog post.
Closes https://github.com/elastic/docs-content-internal/issues/53