Add ingester.skip-metadata-limits flag #6744
Merged
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.
The PR #6681 implements a metadata API query parameter (limit, limit_per_metric, and metric). During a deployment when the querier is on an older version and the ingester is on a new version, the querier always passes 0 values for limits. If then, the ingester returns an empty response.
This PR adds a
-ingester.skip-metadata-limits
flag to make the ingester return metadata during the deployment. After the deployment, set this flag tofalse
to use the metadata API with the limits.Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]