-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emit more histogram buckets for cortex-querier_storegateway_refetches… #6570
base: master
Are you sure you want to change the base?
Conversation
b50d72c
to
e50e81d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -123,7 +123,7 @@ func newBlocksStoreQueryableMetrics(reg prometheus.Registerer) *blocksStoreQuery | |||
Namespace: "cortex", | |||
Name: "querier_storegateway_refetches_per_query", | |||
Help: "Number of re-fetches attempted while querying store-gateway instances due to missing blocks.", | |||
Buckets: []float64{0, 1, 2}, | |||
Buckets: []float64{0, 1, 2, 4, 8, 16}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a customized value of 5 retries. I don't know if it makes sense to have 16 retries. Shall we keep upper limit to 8?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we retry as many times as the user specifies? (https://github.com/cortexproject/cortex/blob/master/pkg/querier/blocks_store_queryable.go#L542)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's right. But I don't think we should recommend users to retry up to 16 times. I mean in general 3 to 7 retries make the most of sense. But maybe that's our usecase.
Do you have a usecase of using that many retries?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, you're right. let's fix it.
e50e81d
to
b3d3e16
Compare
4880120
to
e85f1f9
Compare
CHANGELOG.md
Outdated
@@ -3,6 +3,7 @@ | |||
## master / unreleased | |||
|
|||
* [FEATURE] Querier/Ruler: Add `query_partial_data` and `rules_partial_data` limits to allow queries/rules to be evaluated with data from a single zone, if other zones are not available. #6526 | |||
* [ENHANCEMENT] StoreGateway: Emit more histogram buckets on the `cortex-querier_storegateway_refetches_per_query` metric. #6570 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name should be cortex_querier_storegateway_refetches_per_query
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the catching.
…_per_query Signed-off-by: SungJin1212 <[email protected]>
e85f1f9
to
ed3a42a
Compare
The #6276 exposes consistency check attempts as a flag; this PR emits more histogram buckets on the
cortex-querier_storegateway_refetches_per_query
metric.Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]