Skip to content
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

increase db retain period in ingesters to cover index cache validity period as well #3300

Conversation

sandeepsukhani
Copy link
Contributor

What this PR does / why we need it:
We encountered that internal canaries were reporting missing logs intermittently.
While the logs were there in the storage they were sometimes not being returned in the query results.
Investigating the queries which had the problem I noticed that we were not retaining dbs long enough to cover the expiry of the cached index by queriers. We need to cover the expiry as well since queriers could keep serving chunks for stale index which could be missing recently flushed chunk ids.

I have also refactored the code to simplify the calculations of various durations for boltdb-shipper a bit.

…period as well

refactor ingester store query config to simplify the code
@sandeepsukhani sandeepsukhani force-pushed the boltdb-shipper-ingester-db-retain-period-fix branch 2 times, most recently from 16d1023 to c20dc36 Compare February 9, 2021 09:01
Copy link
Collaborator

@slim-bean slim-bean left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@slim-bean slim-bean merged commit ba25b0f into grafana:master Feb 26, 2021
@pcbl
Copy link

pcbl commented Mar 17, 2021

Hey Folks,
Would this PR solve this issue?

#3214

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants