Skip to content

Conversation

jmikell821
Copy link
Contributor

@jmikell821 jmikell821 commented Mar 26, 2025

Adds uni-directional CCR data stream upgrade instructions to the "prepare to upgrade" section.

Preview here.

Contributes to https://github.com/elastic/docs-projects/issues/247 and https://github.com/elastic/docs-projects/issues/270.

@jmikell821 jmikell821 requested a review from lukewhiting March 26, 2025 04:01
@jmikell821 jmikell821 self-assigned this Mar 26, 2025
Copy link

@lukewhiting lukewhiting left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few possible changes but otherwise this is taking shape nicely :-)


If you want to keep your older data as read only:

1. Issue a rollover for all replicated data streams on the follower cluster to ensure the write index will be compatible with the version you're upgrading to.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Double check with the Kibana team as they may have the migration assistant do this automatically for an ignore now and this step would not longer be required.

Copy link

@lukewhiting lukewhiting left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CCR content looks good from a technical perspective. Will defer to someone with more relevant skills RE the rest of the content.

@jmikell821 jmikell821 merged commit 6b3af62 into main Mar 27, 2025
4 checks passed
@jmikell821 jmikell821 deleted the upgrade-ccr-clusters branch March 27, 2025 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants