-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Timeout when running influx_inspect buildtsi #12890
Comments
Perhaps related (< 100M database), but since either 1.7.4 or 1.7.5 seeing timeouts on all queries and writes and slow memory build up (leak) until restarted and then fine for a few hours. Exactly same work load for last few months, but influxdb version was updated. |
I'm seeing the same issue. After <24 hours, influxdb (running in docker, very tiny DB) stops responding and clients timeout. I'm seeing the same cpu and disk i/o are basically zero, and memory usage is very low. I'll try an older version and see if that fixes it. |
After some more searching, this is probably the same issue as #13010 |
the fix for #13010 is in the 1.7 branch if you are building from source and our plan is to have a 1.7.6 tagged and built next week. |
1.7.6 build is now available. |
Just tried using the 1.7.6 version and get the same issue
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Also hitting the same issue I think...
I have been halving the concurrency down from the default of 24, 12, 6 and each time, it has eventually failed.... I need to drop from series from the DB as the cardinality has gone out of control slowing down all our queries and I cannot do that without converting all the indices.... |
This will be fixed when #14902 is backported to the 1.7 and 1.8 branch. The fix will be part of the 1.7.9 release. |
This can be closed now that #14902 is merged and backported. |
I'm trying to convert to use the tsi1 index and I get the below error.
It seems to be doing lots of things and then it just gets stuck.
I'm using influxdb
1.7.4
We have quite a large DB (69GB) so I'm wondering if this is the issue?
I have also tried it on a single shard and it just times out after a while of doing a lot of activity.
Running an strace on the process produces no output. I just see
And it doesn't seem to be using any CPU etc.
Error is:
Time:
The text was updated successfully, but these errors were encountered: