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
Extreme query start and stop times produce errors #77
Comments
Do you have the errors from the tablet servers? |
Replicated your issue. On the tablet server, the DownsampleIterator creates an array with size based on the number of downsample buckets in your time range. The array can't be larger than Integer.MAX_VALUE. The solution here is to either reduce your time range or increase your downsample time period. |
We should be able to catch this earlier in the query processing and return an error before the query gets submitted to Accumulo. |
I figured something like that was up. That's just the second error or both? |
This actually breaks the web socket idea because we should chunk results over the web socket so timely doesn't need all the results in memory at any time. I'm starting in on the subscription API though, so maybe that's better, I'll see. |
This is vague and probably more of a reminder to look into this more but I've noticed some errors when adjusting the query timestamps while working with the web socket. My guess is it's not a web socket specific thing, but I haven't dug into it. i was using the web socket query operation and timely standalone docker-compose setup for this. Here's what I've captured so far:
setting start time of 0 to stop time of now fails, even with only a little data in the system.
setting stop time far in the future produces an OOM. are result buffers pre-allocated?
The text was updated successfully, but these errors were encountered: