You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
Im having two installations now where InfluxDb is continuously using around 90% CPU. Intitially both systems were running fine. Not sure if its relevant but first instance we had a hardware clock reset by mistake so there was some datapoints registered with very old dates and after that InfluxDb is using around 90% CPU. Second instance we had a faulty network cable and after we fixed communication issue , Influxdb went up to 80% usage.
When I turn of all other read/write access (Telegraf, Grafana) , CPU usage is still around 80-90% so im guessing its some InfluxDb internal process.
Im using InfluxDb 1.7.0
Would appreciate any pointers on how to troubleshoot.
Update 1
Checked all files with influx_inspect with no issues. Made a backup of database and restored it on another computer and cpu utilization went to 90% immediately.
Update #2
Updating from 1.7.0 to 1.7.4 fixes the issues
The text was updated successfully, but these errors were encountered:
Hi
Im having two installations now where InfluxDb is continuously using around 90% CPU. Intitially both systems were running fine. Not sure if its relevant but first instance we had a hardware clock reset by mistake so there was some datapoints registered with very old dates and after that InfluxDb is using around 90% CPU. Second instance we had a faulty network cable and after we fixed communication issue , Influxdb went up to 80% usage.
When I turn of all other read/write access (Telegraf, Grafana) , CPU usage is still around 80-90% so im guessing its some InfluxDb internal process.
Im using InfluxDb 1.7.0
Would appreciate any pointers on how to troubleshoot.
Update 1
Checked all files with influx_inspect with no issues. Made a backup of database and restored it on another computer and cpu utilization went to 90% immediately.
Update #2
Updating from 1.7.0 to 1.7.4 fixes the issues
The text was updated successfully, but these errors were encountered: