docs: announce graceful cluster reconfiguration availability in v26.34.1 (Self-Managed) - #37957
Open
claude[bot] wants to merge 2 commits into
Open
docs: announce graceful cluster reconfiguration availability in v26.34.1 (Self-Managed)#37957claude[bot] wants to merge 2 commits into
claude[bot] wants to merge 2 commits into
Conversation
…4.1 (Self-Managed) Re-add the Graceful Cluster Reconfiguration announcement to the v26.34.1 release notes entry in doc/user/content/releases/_index.md. v26.34.1 backports the fix for the deadlock that had disabled graceful (async) cluster reconfiguration, so the feature is available again on Self-Managed at v26.34.1. Cloud gets it at v26.35. The announcement body is the text previously removed in #37894, restored verbatim under a fresh anchor with a Materialize Self-Managed only marker. The existing Bug Fixes subsection is unchanged. Requested by Pranshu Maheshwari. Language reused from #37894. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019GXtL1FndEDG6gW5f4KLf5
Resolve conflict in doc/user/content/releases/_index.md. main independently added an Asynchronous Cluster Reconfiguration note to the v26.34.1 entry with the same anchor and Self-Managed marker. Reconcile to the single Graceful Cluster Reconfiguration subsection from this PR to avoid duplication. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019GXtL1FndEDG6gW5f4KLf5
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Requested by Pranshu Maheshwari · Slack thread
Motivation
v26.34.1 backports the fix (#37740) for the deadlock that had disabled graceful ("async") cluster reconfiguration, so the feature is usable again on Self-Managed at v26.34.1. Cloud gets it at v26.35. The availability announcement was removed from the docs in #37894 when the feature was deferred out of v26.34. Now that v26.34.1 restores the behavior on Self-Managed, product wants the v26.34.1 release notes to announce it again. Requested by Pranshu Maheshwari, language reused from #37894.
Description
Before, the v26.34.1 release notes listed only the bug fix. After, they also announce that graceful ("async") cluster reconfiguration is available again on Self-Managed.
The change re-adds a Graceful Cluster Reconfiguration subsection to the
## v26.34.1entry indoc/user/content/releases/_index.md, inserted between the release-date line and the existing Bug Fixes subsection. The body restores the announcement text removed in #37894 verbatim (the asyncALTER CLUSTERdescription, theSHOW CLUSTERSexample, themz_cluster_reconfigurationsparagraph and query, and the "Resizing process" link). Two things differ from the removed original. The anchor is a fresh, non-colliding{#v26.34.1-graceful-cluster-reconfiguration}, and a<red>*Materialize Self-Managed only*</red>marker sits directly under the heading, mirroring the file's existing<red>*Materialize Cloud only*</red>convention. The Bug Fixes subsection is untouched. No other files are changed.Verification
This change re-adds previously-shipped release-note text verbatim, so no new automated tests apply. The body is a byte-for-byte restore of the block removed in #37894, with only the anchor and the added platform marker differing. I did not run a full Hugo build because the environment's Hugo is older than the repo's pinned extended v0.152.2 and fails on a pre-existing unrelated shortcode, but since the change only reintroduces text that already lived in this file and passed CI when it originally shipped, a build regression from this edit is not expected.
Consistency note / open questions
doc/user/content/sql/alter-cluster.mdanddoc/user/content/sql/create-cluster.mdto "starting v26.35" with no Cloud-vs-Self-Managed distinction. Those reference docs currently state that graceful, no-downtime resizing starts at v26.35 for everyone. This release note therefore runs slightly ahead of those reference docs for Self-Managed. A follow-up decision is whether those two docs should carve out Self-Managed v26.34.1 vs Cloud v26.35. That is out of scope for this PR.Generated by Claude Code