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

Series fetch issue #146

Closed
bwplotka opened this issue Dec 18, 2017 · 9 comments
Closed

Series fetch issue #146

bwplotka opened this issue Dec 18, 2017 · 9 comments
Labels

Comments

@bwplotka
Copy link
Member

querying store failed: receive series: rpc error: code = Aborted desc = fetch series for block 01C18S2S39ZQ4VK43SKVYBRKSR: invalid remaining size 4096, expected 13485

From time to time.

@bwplotka
Copy link
Member Author

This is on certain query: graph?g0.range_input=2w&g0.end_input=2017-11-23%2013%3A48&g0.expr=go_goroutines&g0.tab=0

(after some time and then 100% reproducible)

@fabxc
Copy link
Collaborator

fabxc commented Dec 18, 2017

This started happening just after you started compaction again?

@bwplotka
Copy link
Member Author

well not really. I was doing lot's of queries for different things and it started on certain query after some time.. so not sure if there is any correlation with compaction. (new compactor is running 1,5h)

@fabxc
Copy link
Collaborator

fabxc commented Dec 18, 2017

Yes, did you ever see this happen before that though?

@bwplotka
Copy link
Member Author

nope

@bwplotka bwplotka added the bug label Dec 18, 2017
@fabxc
Copy link
Collaborator

fabxc commented Dec 18, 2017

I mean this ultimately just seems like some series entries get a good bit longer than the 4KB we expected.
It seems generally possible given we generated a lot of chunks initially with out 5s scrape interval. If you compact a week worth of those together, the series entry has to reference several hundred chunks.

13KB of chunk-indexing data for a single series in a single block actually makes me a bit worried :) But ultimately anything becomes worrisome if you keep the high resolution in long-term storage.

The answer here is basically to just bump the range we fetch per series.

@fabxc
Copy link
Collaborator

fabxc commented Dec 18, 2017

I just hit it as well. It seems indeed to be non-deterministic for the same query over the same time range... that's rather odd though.

@fabxc
Copy link
Collaborator

fabxc commented Dec 19, 2017

Got 'fixed' by bumping the maximum series size we are reading. Anything fully save will require upstream changes to the storage format.

@fabxc fabxc closed this as completed Dec 19, 2017
@bwplotka
Copy link
Member Author

bwplotka commented Dec 6, 2019

Revisiting this as we saw some issues of violating this again e.g #552, plus investigate estimating postings entry size as well here: #1839

Given just one error, it might still not worth to change. Just leaving the calculation for max size of series entry:

rabenhorst added a commit to rabenhorst/thanos that referenced this issue May 4, 2023
* Added float histogram support for receiver

* Fixed lint

* Fixed docs

* Fixed docs
saswatamcode pushed a commit to saswatamcode/thanos that referenced this issue Jan 8, 2025
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Co-authored-by: red-hat-konflux[bot] <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants