-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
[TSDB][Downsampling] NullPointerException on downsampling a TSDB data stream #98792
Comments
Pinging @elastic/es-analytics-geo (Team:Analytics) |
Thanks for sharing this. This looks strange. The NPE suggest that the index doesn't the index.time_series.start_time or end_time setting, which is strange. Since this is required for tsdb indices. |
For some reasons if I try to retrieve settings for the index before starting downsampling it is missing some time series required settings like start and end time
I used the following script
|
I've tried again with a recent ES snapshot to run the script above and now it hangs at first downsample task:
On the script side I have this:
|
Fixed by #98840. |
Elasticsearch Version
8.11.0
Installed Plugins
No response
Java Version
bundled
OS Version
MacOS
Problem Description
This problem surfaced since the beginning, but since #98587 it got much worst.
In Kibana there are some tests to check for TSDB downsampled data streams, which have been disabled before the bug that #98587 fixed, and now we're trying to restore them back: elastic/kibana#164410
The CI is reporting failures on the TSDB downsampling tests with errors related to a
NullPointerException
:The log shows how the data stream being created, documents added, then rolled over to obtain an index to write block to perform a rollover before the downsampling: the first downsampling request fails with the
NullPointerException: text
error, then a new attempt is made with the same error, but this time the downsampled index seems to exists.Steps to Reproduce
I've put together a simple script that performs the steps 10 times and it the error will randomly appear:
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: