Delayed InfluxDB® Server Initialization
If the InfluxDB® server's initialization is delayed, hindering its connection to the NGA, examining database logs can provide valuable insights.
For detailed instructions on how to access and interpret these logs, please refer to the chapter InfluxDB® Database Logs. Consider also the config entry when you must deal with longer database startup times.
Factors influencing server startup duration
| Factors influencing server startup duration | Description |
|---|---|
| Number of shards and amount of data | This is represented in NGA by group segments.
The shards are scanned during startup. The more segments and data they contain, the longer it takes to start the database. |
| High cardinality | Cardinality is defined as the number of unique series in your
database.
A unique series is a combination of the measurement and tag values. In NGA, this is proportional to the number of archive configs (and the number of NGA groups assigned to each archive config). Both performance and startup times deteriorate as cardinality increases. |
| Hardware resources | The hard disk I/O bandwidth and the amount of available RAM have
a major impact on server startup times.
We recommend ensuring that good SSDs are used and that sufficient memory is available. The use of these resources must be monitored during database startup. Also, ensure that no other application running on the server machine is consuming too many hardware resources. |
