influxdata / influxdata/influxdb

InfluxDB 2.3 -> 2.7 : Slow start time caused by number of checks

Open
#24,958 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

# InfluxDB 2.3 -> 2.7 : Slow start time caused by number of checks
## The issue
I recently migrated from Docker image influx:2.3 to influx:2.7.

I never had issue with the start time of 2.3. After migrating to 2.7, start time would increase from a couple seconds (2-3 seconds) to more than 10 minutes.

After investigation, I found out that the start time in 2.7 is directly proportional to number of Checks which is not the case in 2.3

## Step to reproduce
1. Add many checks (>100)
2. Wait a couple hours. (Problem does not arise immediately after check creation)
3. Restart Influx container
4. Notice the slow start time
5. Remove all checks
6. Restart Influx container
7. Notice almost immediate start time

*note: by start time I mean the time between the container creation and Influx tcp-listener start

Contributor guide

Open the contributing guide

Research direction

Reproduce the startup behavior with the influx:2.3 and influx:2.7 Docker images, using more than 100 checks and waiting before restarting the container. Compare the time until the Influx TCP listener starts; done means startup no longer increases substantially with the number of checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.