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
Include missing file data if querier fails to find trace by ID #1730
Comments
This is not a bad idea. I think we could probably wrap errors in these methods to include information about the requested objects: Lines 116 to 131 in 9a135a9
|
Oof, scratch that. We check the return of a lot of these methods with statements like:
If we wrapped the error on the lines recommended above it would break these checks. Perhaps it would be better just to make the log change where we request the bloom filters:
|
Cool I'll take a look |
Is your feature request related to a problem? Please describe.
In the event you have corruption within a folder, for instance if bloom files are missing, querier will fail to iterate over it and then log a somewhat opaque error like the following:
Describe the solution you'd like
A list of the bloom files or other files, or even a subset of those files if the list is long, would be helpful debugging info.
Describe alternatives you've considered
You can examine the folder to see if the bloom files do not miss a number.
Additional context
If this is irrelevant with the parquet backend, we can close.
The text was updated successfully, but these errors were encountered: