Various configurations
The publishing queue is a table in the database, so the rule is one daemon per database. Two daemons reading the same queue would take the same drafts.
| Setup | Daemons |
|---|---|
| One server, one installation, one database | One daemon. |
| One server, several installations, each with its own database | One daemon per installation, each started by its own init script link or systemd service, each with its own PID file. |
| Several servers, one installation (a cluster), one database | One daemon, on one of the servers only. |
| Several siteaccesses of one installation | One daemon: the siteaccesses share the database and the queue. |
The daemon locks its PID file, so a second daemon with the same PID file does not start. That protects one server only: on a cluster, make sure only one server runs the service.
How many drafts one daemon publishes at the same time is set with content.ini [PublishingSettings] PublishingProcessSlots (10 as shipped). See Setting up the asynchronous publishing service.
Contributors
- Geir Arne Waaler
- Graham Brookins Updated Maintainer
Comments
Add a comment