Current State of Icinga DB
summary
Stable release three weeks old replaces IDO with a new architecture using Redis + SQL (MySQL/Postgres), sending configuration and runtime updates to Redis and a single db daemon that syncs via hash IDs and uses 16 DB connections and bulk upserts to avoid dependent inserts. Tests show roughly a 10–15× speedup on restarts; history writes only on state changes, with Redis streams for durability. Supports HA with two masters/two Redis and one central database; migration tooling for old history is forthcoming.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:40Who is Eric
- 1:08Why Single DB
- 8:16Redis
- 9:51AsyncDB
- 14:15Database
- 16:00Single DB Web
- 19:00High Availability
- 20:57Multiple Environments
- 25:12Migrating to Single DB
- 27:29Single DB Performance
- 30:11Check Frequency
- 31:46Icinga for Radius
- 32:49Questions
- 35:29Is it possible to run a single DB in parallel
