-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Query: Allow to ignore No StoreAPIs matched error #5937
Conversation
I am not sure if this is a good idea to apply by default. In rulers we usually want to catch errors like this one. However, having a flag to disable this warning might be something useful. |
Mhm, I wonder if this is not some issue introduced during the recent proxy.go refactoring. See #5862. It's probably better to investigate what behaviour has changed between versions instead of adding yet another option :/ |
I reproduce the No StoresAPIs matched error by running receive with an ingester mode and a nonexistent datadir and then using querier to query it before it receives any remote write requests. It has no stores (did not create a tsdb store for the default tenant id) and but still receive query requests and send the error back to querier. |
If the configured datadir not exists, receive ingester will not create a default tenant data dir and not create tsdb store for the default tenant id when open MultiTSDB, so it have no any stores but has an infinite TimeRange(MinInt64->MaxInt64) and then can receive query requests from querier. This may be a special one of cases mentioned by 5862#issuecomment-1312296482. |
Hello 👋 Looks like there was no activity on this amazing PR for the last 30 days. |
Ping, is this still being worked on? |
Possibly related issue: #5230 (comment) |
Signed-off-by: junot <[email protected]>
Signed-off-by: junot <[email protected]>
conflicts resolved and changelog added |
Do we actually need to plumb in a configuration option for this? Based on the discussion so far, this is a simple bug and we can just make the change. |
@SuperQ You mean we can directly |
I think so. I created #6082 as an alternate proposal. |
Make sense, no error should be returned if no store matched |
Changes
Add
ignore_no_stores_matched
param to Query APIs to allow to ignoreNo StoreAPIs matched error
(default to be specified by--query.ignore-no-stores-matched
flag). The query param is also to added to grpc series request for ignoring the same error.It may fix the issue #5862 .
Verification