Components and reliability¶
An Optic installation consists of a few components, each with its own stored state and guarantees. This page describes state storage, the effects of failures and upgrade compatibility. The cluster's behavior during a central outage is covered separately — Streamer autonomy.
What the installation consists of¶
- The optic service on the central machine — the control plane and the local streamer in one process.
- PostgreSQL — central's state store. It stores the group's configuration and registries.
- The streamer services — broadcasting; each has its own state directory and archive disks.
- The metrics store — built-in, in process memory, retaining a few hours of chart history, not an archive.
What is stored in PostgreSQL¶
The installation's configured state and records:
- stream configurations and streamer configs;
- the streamer registry — records with the machines' identity and keys;
- the stream placement, the decision journal and the layouter runs;
- the closed sessions journal;
- central's TLS material — the ACME account and the issued certificates.
A database backup lets you restore the group's configuration and registries. For instructions, see Backup and restore.
What is stored on a streamer¶
The /var/lib/optic state directory of every machine:
server.idand the activation cache — the machine's licensing identity;- the streamer's cluster identity — the key it presents itself to central with;
- the cache of the applied configuration slice — what powers the warm start without central;
- the local journal of closed sessions until central harvests it.
The DVR archive is stored separately — on the dedicated disks set in the streamer settings.
What survives the loss of what¶
| Lost | What happens | What to do |
|---|---|---|
| All reachable central instances | Broadcasting and recording continue; management and playback through central are unavailable | Streamer autonomy; connections recover automatically after the process starts |
| The PostgreSQL database | As above, plus the configured state is lost | Restore from a dump — streamers reconnect automatically |
| The database, with no backup | Broadcasting continues; streamers have lost their registration | Join each one again: reset state and use a fresh token |
| A streamer's state directory | The machine loses its licensing and cluster identity | Join the machine again; streams will be reassigned |
| A DVR disk | That disk's archive is lost; broadcasting is unaffected | Disk indicators in diagnostics |
| The metrics store (a process restart) | A few hours of chart history are lost | Nothing — data accumulates again |
Compatibility guarantees¶
- Different versions coexist. The wire protocol only grows by addition: unknown fields must be ignored by both sides, so central and streamers of neighboring versions work together.
- The database schema is compatible within a two-version window. A newer schema under older code is the norm; that enables both a staged upgrade and a binary rollback without a database rollback.
- Registration is deliberately non-idempotent. Joining the same machine again creates a new registry record, and
server_idduplicates are marked by the registry with the decision left to the operator.