-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Index Corruption During Large Import #303
Comments
Hi @kierangirvan |
Thanks. My advice would be to try to upgrade to v5 as this uses a newer version of timescaledb. But to be fair, I have no idea, whether this going to solve your problem or not :| |
We've decided to completely rebuild the service (unfortunately meaning we lose our previous tests), but this seems to have introduced a new issue: |
What kind of database image do you use? it looks like you are not using the one from here https://github.com/ludeknovy/jtl-reporter/blob/main/db/Dockerfile |
I've just recreated this cloning the main branch, docker-compose up and attempting to import a tiny jtl file: |
My cloud engineer shared the following from our AWS hosted jtl reporter, this is the same as my local install: |
lttb function missing means, you dont have the timescale db toolkit installed. |
I have fed this back to the cloud engineer, I'll let you know if this fixes the issue. Obviously the original error in this ticket is still a concern, and we had to entirely rebuild the stack therefore losing all of our historical tests. |
But why didnt you make a backup of your data?? |
We do have backups of the jtl files, so we can re-upload them. |
Describe the bug
We regularly import a large jtl file post test (we've previously discussed importing/feeding the file during the test but this is not possible). But the import seems to work just fine however, we have recently increased our load profile meaning the jtl file has jumped from 800mb to 1gb and as a result we are seeing an index corruption message in the BE logs.
{"level":"error","message":"Error occurred during data parsing and saving into database: error: index \"_hyper_1_14_chunk_samples_item_idx\" contains unexpected zero page at block 28401, item_id: fb38060d-63a9-4703-b278-5a972734d624"}
We have reindexes this index and tried to import again and it fails with the same error message.
To Reproduce
Try and import a large (>1gb) jtl file
Expected behavior
The jtl file to successfully upload.
Screenshots
The text was updated successfully, but these errors were encountered: