Document minTargetHits resolution formula and grouped topology interaction - #4810
Open
sarzhann wants to merge 1 commit into
Open
Document minTargetHits resolution formula and grouped topology interaction#4810sarzhann wants to merge 1 commit into
sarzhann wants to merge 1 commit into
Conversation
…tion Customers on SUPPORT-779 had to ask twice, and needed engineering to clarify, how totalTargetHits and minTargetHits resolve to a per-node target hits value, and why the node's document share is relative to its group rather than the whole cluster. The existing reference entry did not state the formula or the common pitfall where minTargetHits silently overrides totalTargetHits after moving to a grouped topology. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
Adds an explanation to the
minTargetHitsreference entry inyql.htmlcovering the exact per-node resolution formula (max(minTargetHits, ceil(totalTargetHits × share))), thatshareis relative to the node's group rather than the whole cluster, and a note on the common pitfall whereminTargetHitssilently overridestotalTargetHitsafter moving to a grouped topology.Why
Customers migrating to grouped content clusters had to ask twice, and needed direct engineering input, to understand how
totalTargetHitsandminTargetHitsresolve to a per-node value and why the denominator is the group's node count, not the cluster's. The reference page did not state the formula or the topology-dependent pitfall, so support had to explain it ad hoc each time.