[Bug] Fixes issue where the combiner can return no data when max series is hit#6099
Merged
joe-elliott merged 2 commits intomainfrom Dec 18, 2025
Merged
[Bug] Fixes issue where the combiner can return no data when max series is hit#6099joe-elliott merged 2 commits intomainfrom
joe-elliott merged 2 commits intomainfrom
Conversation
… was hit Signed-off-by: Joe Elliott <number101010@gmail.com>
javiermolinar
approved these changes
Dec 18, 2025
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.
What this PR does:
This issue was discovered while working on integration tests and would be difficult but not impossible to trip in a real environment. If the combiner hit max series but had not yet received it's metadata response then it would still return true from shouldQuit(). This caused it to return an empty response when GRPCDiff() was called b/c it didn't think it had any complete data.
Also added a note about using GRPCFinal(). That was changed here, but perhaps we should revisit. Grafana has added the ability to accept larger websocket payloads and sending a complete final message would avoid bugs like this.
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]