Start/notes.ini Parameters/RTR_Logging

RTR_Logging

Profile

Parameter
RTR_Logging
Category
Cluster
Component
Server
Available since
9.0.1 (and earlier); HCL KB0037704 explicitly mentions Domino 9.0.x, 10.0.x, 11.0.x and higher
Supported versions
9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1
GUI equivalent
notes.ini only (no GUI)
Possible values
0 = off (default) • 1 = enable status messages • higher values = more detail (per the HCL guide “Enabling the display of cluster replication status messages”)

Description

RTR_Logging enables an extended logging output of the cluster replicator (clrepl). By default, a cluster server logs its replication activity hourly or on demand (tell clrepl log) — the depth of this default output is limited and essentially names the databases replicated between cluster servers.
With RTR_Logging=1 (or higher), additional cluster-replicator status messages appear on the server console and in the log:
  • Current processing state of the cluster-replicator queue,
  • Statistics on replication of individual databases and objects,
  • More detailed error messages for rejected or failed replications.
In HCL KB KB0037704 “Additional Cluster Replication Logging Parameters”, RTR_Logging is recommended together with Log_Replication as the standard path for deeper diagnostics of cluster-replication problems — especially when the standard output of Log_Replication alone is not sufficient. The associated guide in the HCL Product Documentation is titled “Enabling the display of cluster replication status messages”.

Example configuration

Enable cluster-replicator status messages (typical diagnostic configuration):
RTR_Logging=1
Log_Replication=2
Runtime activation via the server console:
set config RTR_Logging=1
set config Log_Replication=2
Return to defaults after diagnostics:
set config RTR_Logging=0
set config Log_Replication=1

Notes & pitfalls

  • Effective only on cluster servers; on non-cluster servers, the parameter produces no additional output, since the clrepl task does not run there.
  • Higher values can produce a considerable log volume on the console and in log.nsf/console.log — sensible to combine with CONSOLE_LOG_MAX_KBYTES=… and targeted diagnostic windows.
  • Should be set together with Log_Replication=2 (or higher) to also log the underlying replicator activity.
  • Usually takes effect immediately via set config RTR_Logging=…; a restart is not required.
  • For interactive display of current cluster-replication statistics, Domino additionally offers tell clrepl log and show stat replica.cluster.*.
  • After completing diagnostics, explicitly reset to 0 — otherwise the increased logging continues running indefinitely.

Sources (HCL Product Documentation)