Content Server Manual / Version 2204
Table Of ContentsMalfunctions that occur on the Replication Live Server can affect two components:
replication: Replication is interrupted and the content of the Replication Live Server becomes outdated depending on the publication activity of the Content Management Server . After restart, the Replication Live Server continues replication at precisely the point where it was interrupted and will only go online when its content is up to date.
Content Application Engines: Not running CAEs fail to start and running CAEs return errors when requesting the Replication Live Server . After restart, CAEs can reconnect. They don't need to be restarted.
| Replication Live Server Failure | |
|---|---|
| Error behavior | All CAEs connected to the Replication Live Server receive connection error responses from the server. |
| Error correction |
The Spring Boot health actuator on the
Replication Live Server
has a subpath actuator/health/replicator which will return a non 200 HTTP return code
in case the replicator reports a problem. Depending on the deployment, this health check can be used
to automatically restart the server. As soon as the
Replication Live Server
is online again, the CAEs are working properly again.
|
Table 2.4. Replication Live Server failure
| Replication Live Server Database Failure | |
|---|---|
| Error behavior | Transactions which are active at the time of failure or which first notice the failure are terminated with an error. The error is passed to the server and clients. A replicator client is terminated. Requests to CAE clients fail with an error. Transactions started after the server has detected the database failure are blocked until a new database connection is created. Requests to CAEs are paused. Appropriate messages are written to the server log. |
| Error correction |
Because a database failure can lead to erroneously generated pages or blocked requests, restarting the Replication Live Server is required.
To restart the
Replication Live Server
,
a cluster management can use the available health indicators provided at the Spring Boot actuator health endpoint
at |
Table 2.5. Database failure
