-
Notifications
You must be signed in to change notification settings - Fork 818
Querying basis on filter and getting metrics we should'nt get #5709
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
Comments
It would be great to provide steps to reproduce the issue. Otherwise it would be hard for us to figure it out. What was the time range you are querying? And it should only query ingester, not store gateway? |
@Marcusfve also include the config if you can. hiding out secrets, of course. |
I rly dont have the steps to reproduce the issue...because it randomly happened and have no idea how to reproduce it. The time range was first 13 hours (that is the time range it sends queries to ingesters). We are running cortex in docker swarm cluster and the config is following:
Please if you need more information, just ask. And i would rly appreciate if you take a look on my config as overall and make suggestions to make something better, maybe i have missed something important. |
Do you still have the bad TSDBs? |
I do not have the bad TSDBs anymore, but as i said i was able to fix this issue by cleaning ingester volume, maybe this can give you some hint. |
Very related to #5419 |
We had maintenance yesterday and suddenly we are seeing in our system, metrics which we are querying basis on filter, result is having data of other metrics & filters too. Not sure why query is not fetching correct data. We are querying data which is in Ingester only and we are running cortex 1.16 version.
Problem started after maintenance was done and machines all the machines were restarted.
One hour after the maintenance i got an alert
CortexIngesterTSDBHeadCompactionFailed
This is what we got when we queried the data. Some metrics shouldnt be there.

Im thinking maybe ingesters were affected by the force shutdown..
Right now i was able to fix this issue by cleaning ingester volume but i want to know why this happened in the first place and what i can do to prevent this issue.
If you need any more information then please, be free to ask.
The text was updated successfully, but these errors were encountered: