Start/notes.ini Parameters/DEBUG_CLUSTER

DEBUG_CLUSTER

🛠️
Parameter: DEBUG_CLUSTER
Short description: Debug output for the cluster components (Cluster Manager, Cluster Replicator, Cluster Probes) – shows failover decisions and member availability.

Profile

Parameter
DEBUG_CLUSTER
Category
Logging / Debug
Component
Server
Available since
10.0
Supported versions
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 = basic, 2 = verbose

Description

A Domino cluster involves several components: the Cluster Manager monitors member availability via probes, the Cluster Replicator (clrepl) replicates data in real time between cluster members, and the Cluster Database Directory (cldbdir) manages cldbdir.nsf. DEBUG_CLUSTER writes detailed trace output for exactly these actions – failover decisions, probe responses, replication queues, conflict detection.
Important for questions such as Why didn't server A fail over to server B? or Why is cluster replication hanging?.

Example configuration

DEBUG_CLUSTER=2
Debug_Outfile=/local/notesdata/IBM_TECHNICAL_SUPPORT/cluster_debug.log

Notes & pitfalls

  • Level 2 is very verbose – enable only temporarily on production clusters.
  • Entries appear in console.log and optionally in Debug_Outfile.
  • Takes effect immediately via set config DEBUG_CLUSTER=2; a restart is not strictly required.
  • Complementary to Cluster_Probe_Min_Hours, Cluster_Probe_Timeout, Server_Availability_Threshold, Debug_Outfile.
  • For probe issues, additionally evaluate tell clrepl show queue and show cluster.