Restarts the Replicator sessions if lost (true).

Whether the replicator checks that the hashes of uploaded blobs are the same as the hashes stored on the Master Live Server. A failed check indicates that the blob store configuration differs between the Master Live Server and the Replication Live Server. Defaults to true. Only set to false to force replication to resume in case of an emergency. The resulting inconsistent blobs ids may affect blob retrieval and the affected Replication Live Server should be recreated afterwards.

Defines if the Replication Live Server checks the event queue for connection (true). The event stream is not checked during the initial replication.

The time in seconds after which the Replication Live Server checks the event queue for connection.

Sets the maximum number of events that is fetched from the Master Live Server in one chunk during startup; 0 indicates no limit. Lowering the threshold will reduce main memory consumption at the cost of startup times.

Defines if the Replicator should be started on start of the Replication Live Server (true).

Switch to runlevel online even if the repository contents have not yet been replicated from the Master Live Server. Ignored if not cap.server.init-runlevel=online.

All repository events will be logged (true).

If the Replication Live Server is offline after a consistent replication but it is more than the given number of events behind the current timestamp, then the Replication Live Server will not go online until it catches up.

Sets the maximum number of events that the packager holds in main memory before flushing to disk. Lowering the flush size will reduce main memory consumption at the cost of write performance.

Configures the password to authenticate against the Master Live Server.

Sets the location where the Replicator can find the IOR of the Master Live Server.

Restart the Replicator if an error occurs on Replication Live Server side (true). Otherwise, the Replicator will be stopped.

Stop the Replication Live Server if an error occurs on Replication Live Server side.

Defines if the Replication Live Server waits on start for the Replicator to connect to the Master Live Server.

The path to the folder where the Replication Live Server should write temporary data during replication.

The path is relative to the installation directory of the replicator application, so you will probably use an absolute path. During initial replication of a complete repository, a huge amount of data will be written to this directory, in the order of the repository size. So, this directory should be located on a suitable file system with enough space left. During normal operation, only newly published blob content will be buffered on local disk

Configures the user name to authenticate against the Master Live Server.