From 515ae6b3fa2f0503e3862bd9e381192c58574690 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 6 Oct 2023 17:10:37 +0100 Subject: [PATCH] Update product_docs/docs/pgd/5/node_management/node_recovery.mdx Co-authored-by: Josh Heyer <63653723+josh-heyer@users.noreply.github.com> --- product_docs/docs/pgd/5/node_management/node_recovery.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/node_management/node_recovery.mdx b/product_docs/docs/pgd/5/node_management/node_recovery.mdx index 8dfc6a533ce..73864c9b3c3 100644 --- a/product_docs/docs/pgd/5/node_management/node_recovery.mdx +++ b/product_docs/docs/pgd/5/node_management/node_recovery.mdx @@ -40,7 +40,7 @@ vacuuming of catalog tables. On EDB Postgres Extended Server and EDB Postgres Advanced Server, offline nodes also hold back freezing of data to prevent losing conflict-resolution data -(see [Origin conflict detection](consistency/conflicts)). +(see [Origin conflict detection](../consistency/conflicts)). Administrators must monitor for node outages (see [monitoring](monitoring/)) and make sure nodes have enough free disk space. If the workload is