[Doc] Clarify multi-tenant data management opt-in and merge config flag (release-4.1 notes)#72358
Open
celerdata2308 wants to merge 1 commit into
Open
[Doc] Clarify multi-tenant data management opt-in and merge config flag (release-4.1 notes)#72358celerdata2308 wants to merge 1 commit into
celerdata2308 wants to merge 1 commit into
Conversation
The original 4.1 release-note entry for the New Multi-Tenant Data
Management feature understated three caveats that surfaced during
internal validation and code review:
- The feature is opt-in via FE config 'enable_range_distribution = true'
(default 'false'). Upgrading to 4.1 alone does not activate it.
- Tablet split is automatic and triggered by a configured size threshold
('tablet_reshard_target_size', default 10 GB). The original wording
'oversized or hotspots' implied access-pattern hotspot detection that
is not present in the runtime.
- Tablet merge is also implemented in 4.1 but ships behind a separate
config flag ('tablet_reshard_enable_tablet_merge', default 'false').
The original wording 'automatic splitting and merging' did not reflect
that merge requires explicit opt-in.
This change clarifies both the opt-in nature of the feature and the
correct trigger semantics, in en/zh/ja release notes.
Contributor
[Java-Extensions Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
Contributor
[FE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
Contributor
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
Contributor
🌎 Translation Required?✅ All translation files are up to date.
|
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.
What
Updates the New Multi-Tenant Data Management entry in the StarRocks 4.1 release notes (en/zh/ja) to clarify three caveats that surfaced during internal validation and code review at
branch-4.1.0tag:enable_range_distribution = true(FE config, defaultfalse). Upgrading to 4.1 alone does not activate the behavior.TabletReshardUtils.needSplit/TabletStatMgr.triggerTabletReshard) only checkstablet_reshard_target_size(default 10 GB).branch-4.1.0confirmsMergeTabletJobruntime + auto-trigger logic inTabletStatMgr.triggerTabletReshardboth ship in 4.1.0, but the feature is gated bytablet_reshard_enable_tablet_merge(defaultfalse). The original wording "automatic splitting and merging" implied merge was on by default.Why
The original release-notes wording overpromised the feature's default behavior. Customers reading the notes today and upgrading to 4.1 without setting either FE config will not observe any automatic tablet reshape, and would reasonably file bugs.
Files changed
docs/en/release_notes/release-4.1.mddocs/zh/release_notes/release-4.1.mddocs/ja/release_notes/release-4.1.mdReviewers
cc @DanRoscigno @EsoragotoSpirit for docs review.
Behavior change classification
Backport