What it means
The Cluster Replicator could not push a change to the replica on another cluster member. It retries automatically until it succeeds.
Common causes
- The other cluster server is down, restarting or overloaded
- Network problems on the cluster replication path
- The destination replica is unavailable, damaged or has too little ACL access for the source server
Quick fixes
- Run
show cluster and check the other member is up and reachable
- Once the problem is fixed, run
tell clrepl retry to retry failed replications straight away
- Run
show stat replica.cluster* to check for a backlog or repeated failures
- Check the destination replica opens and its ACL gives the source server enough access
Disclaimer
The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.
This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.