-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Starting takes a long time with InfluxDB API unavailable messages after 2.7.6 to 2.7.7 upgrade #25159
Comments
There weren't any changes between 2.7.6 and 2.7.7 that obviously affect start-up time (of course, with things like a Go version upgrade, all sorts of components may be different in ways that are outside of our control). I don't see any errors in your startup log, so no indication that anything is wrong. Could you attach a log from a 2.7.6 boot sequence for comparison? |
Of course. This is de fast startup with 2.7.6
|
The difference I am seeing here is the |
Yes, with 2.7.6 I forgot to set debug level. But before I saw the same bucket find messages. Also after start. So it looks some regular task. |
I'm using Ubuntu 20.04.2 LTS with influxdb 2.7.6-1 and after an upgrade starting influxdb takes a long time with a lot of "InfluxDB API at http://localhost:8086/ready unavailable after xx attempts" messages
This also happens when I start influxdb with all buckets removed.
If I downgrade to 2.7.6-1 I don't have any problems anymore.
Steps to reproduce:
List the minimal actions needed to reproduce the behaviour.
Expected behaviour:
Starting command (3) will return in a few seconds.
Actual behaviour:
It takes a long time (2-5 minutes) before the starting command returns. In de mean time I see a lot "InfluxDB API at http://localhost:8086/ready unavailable after xx attempts" messages. In the end it will start.
My VM has 2 GB mem. Then it will take about 500 attempts. When increasing to 3 GB, it will take about 150 attempts. Influxdb takes a lot of memory and CPU during startup.
Environment info:
root@ubuntu1-Copy2:~# uname -srm
Linux 5.4.0-74-generic x86_64
Using a VM on ESXi with 2 CPU and 3 GB memory.
Config:
root@ubuntu1-Copy2:~# cat /var/lib/influxdb/.influxdbv2/config.toml
bolt-path = "/var/lib/influxdb/.influxdbv2/influxd.bolt"
engine-path = "/var/lib/influxdb/.influxdbv2/engine"
http-bind-address = ":8086"
storage-series-id-set-cache-size = 100
session-renew-disabled = true
session-length = 1440 # session renewal after 1 day
Logs:
Logging with debug level and with all buckets removed.
The text was updated successfully, but these errors were encountered: