docs: tweak swap upgrade instructions #34126
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kay-kim
commented
Nov 14, 2025
| Swap allows for infrequently accessed data to be moved from memory to disk. Enabling swap reduces the memory required to operate Materialize and improves cost efficiency. Upgrades to v26 and later have swap enabled by default. | ||
|
|
||
| ## Upgrading to v26 with swap requires node preparation | ||
| We've added new labels to the node selectors for clusterd pods to enable smooth upgrades. As a result, if you are running v25.2.12 or earlier, your existing nodes will not match these selectors and won't be selected to run the pods. Before upgrading to v26, you must prepare your nodes by adding the required labels. |
Contributor
Author
There was a problem hiding this comment.
Q: is the v25.2.12 or earlier correct? Just asking because we're currently at v25.2.15 per
https://materializeinc.github.io/materialize/index.yaml and so the title of these pages and blurbs are a little weird.
Contributor
There was a problem hiding this comment.
Yes this isn't refering to the latest version it's referring to the version of the self-managed where the orchestrator /helm chart were updated to add labels.
Contributor
Author
There was a problem hiding this comment.
So then, it is correct for people to just use the regular upgrade (sure, currently, on this branch legacy TF) if they're at, let's say, v25.2.15?
maheshwarip
reviewed
Nov 14, 2025
doc/user/content/installation/install-on-aws/upgrade-to-swap.md
Outdated
Show resolved
Hide resolved
Contributor
|
@kay-kim looks like we have merge conflicts on this one |
Contributor
|
ok merge conflicts should be fixed! |
maheshwarip
approved these changes
Nov 14, 2025
maheshwarip
merged commit 6189722
into
MaterializeInc:docs-upcoming-v26.0.0
10 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.