-
Notifications
You must be signed in to change notification settings - Fork 814
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
Querier segfault #4390
Comments
I had the same behaviour upgrading our Cortex environment from v1.9.0 to v1.10.0. My dev environment is running 1 instance of each microservice on a single EC2 instance (CentOS 7). We're running block storage (S3) with the following services: alertmanager, compactor, distributor, ingester, querier, ruler, store-gateway. After upgrading all services to v1.10.0 we started seeing the below panic from the Querier service only.
|
Same for me on release 1.10 |
Same for us after upgrading from 1.9 to 1.10 using block storage and only one tenant. |
@RicardoNalesAmato I've worked this around by replacing a function that serves Exemplar with a stub that returns nothing as we don't need them. |
I believe this is fixed by #4473. |
Do you happen to use |
@pstibrany We will try that fix in our staging cluster. Thanks! |
I can confirm that deploying a version of cortex that includes #4473 has fixed the issue for us |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
Describe the bug
Observed panics due to segmentation faults in the querier.
To Reproduce
Run cortex v1.10.0-rc1 and utilize the querier
Environment:
Storage Engine
Additional Context
The text was updated successfully, but these errors were encountered: