Medusa Panel › Server › Manage Servers
Medusa scales by spreading work across several servers. The server you log into is the master; every other server you add is a worker (slave) that runs streams and adapters and serves the CDN. One panel controls them all.
What the master does
The master holds the panel and the database and coordinates the cluster. A stream or a DVB adapter runs on the server it is bound to; the master tells that server to start and stop it, forwards its control and logs, and relays SAT>IP discovery to the server that owns the tuner. You never log into a worker to operate it — you drive everything from the master.
Shared configuration
Configuration is kept in step automatically. When you change a stream, profile or setting on the master, it reloads and notifies the other servers, so every node sees the same configuration. A node that reconnects after a drop reloads everything, so it never misses a change made while it was away.
What a node can do
- Streaming worker — runs streams and adapters (its own tuners, GPUs and CPU).
- CDN node — serves packaged output to viewers. Toggle this per server with the CDN Service switch.
- Both — a server can transcode and deliver at the same time.
Related
- Adding nodes — register and install a worker.
- Built-in CDN — serve output from every node.
- Load balancing and metrics — spread viewers across nodes.