[v25.3.x] config: add features_auto_finalization enterprise property#30461
Merged
Conversation
pgellert
approved these changes
May 14, 2026
Adds a cluster configuration knob to defer cluster active logical version advance until explicit operator action via the admin API. Default `true` preserves existing behavior; setting to `false` enables the new manual-finalization flow, which is gated by an Enterprise license via the `enterprise<>` property wrapper. Independent of `features_auto_enable`, which separately governs per-feature auto-activation after the version advance. The gating logic that consumes this property lands in a follow-up commit. The configuration option is made a non-user-visible tunable in 25.3.x because it is a noop until 26.2 but we want users to still be able to set it prior to starting a multi-verison-hop upgrade sequence. In 26.1 it is a normal, user-visible configuration option. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
9cf2c38 to
d67bc66
Compare
Member
Author
|
@pgellert i made the option a tunable instead of a user-visible config in 25.3 since it's a noop in the 25.3->26.1 hop but still useful to be able to set prior to a multi-hop upgrade sequence. In 26.1 its normal user visiblilty. |
WillemKauf
approved these changes
May 14, 2026
Collaborator
Retry command for Build#84459please wait until all jobs are finished before running the slash command |
Collaborator
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
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.
Manual backport of commit 90cfd44 from PR #30324, scoped to just the
features_auto_finalizationcluster configuration option.Backporting only the configuration knob (not the gating logic that
consumes it) lets operators on earlier releases set
features_auto_finalization=falsebefore upgrading to v26.2, wherethe manual-finalization flow ships. Without this backport, customers
would have to upgrade to v26.2 first and would lose the ability to
defer the active version advance before reaching the new minor.
Note that customers must be running this minor (or later) before the
major upgrade to v26.2 in order to make use of the manual
finalization flow.
Tracked in CORE-16305.
Original PR: #30324.
Backports Required
Release Notes
Improvements
features_auto_finalizationcluster configuration option to allow opting out of automatic upgrade finalization before upgrading to v26.2.