From fa44ee0836c5cbef678730d22a210b15b48b2402 Mon Sep 17 00:00:00 2001 From: Balazs Lendvai Date: Fri, 5 Sep 2025 12:54:29 +0200 Subject: [PATCH 1/2] Remove problematic part from `unbind` docs --- .../ROOT/pages/clustering/clustering-advanced/unbind.adoc | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc b/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc index 4319e5690..30f18b62a 100644 --- a/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc +++ b/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc @@ -12,7 +12,9 @@ Therefore, it is strongly recommended to consult with Neo4j Support before using Use the `unbind` command only when troubleshooting **a specific server** and remember there is no guarantee that the allocator will reassign the same databases to this server, potentially resulting in orphaned database stores. -The `unbind` command preserves all database stores on the server; and when the unbound server is restarted and enabled, it is seen as an entirely new server. +The `unbind` command preserves all database stores on the server; and when the unbound server is restarted, it is seen as an entirely new server - so it won't host any of the database it did host before the operation. + +The `unbind` command can't be used anymore to convert a cluster member into a standalone server. For that we recommend taking backups, create the standalone server and the use those backups to create the databases. ==== [[unbind-command-syntax]] @@ -79,10 +81,6 @@ You can use the `neo4j-admin server unbind` command to remove the cluster state To remove the cluster state of a server, run the `neo4j-admin server unbind` command from the __ folder of that server. When restarted, an unbound server rejoins the cluster as a new server and has to be enabled using the `ENABLE SERVER` command. -=== Turn a cluster member into a standalone server - -To start the Neo4j server in single (standalone) mode after unbinding it from the cluster, verify that xref:configuration/configuration-settings.adoc#config_initial.server.mode_constraint[`initial.server.mode_constraint`] is set to `NONE` in xref:configuration/neo4j-conf.adoc[The neo4j.conf file]. - === Archive cluster state If something goes wrong and debugging is needed, you can archive the cluster state, from the __ folder, run the `neo4j-admin server unbind` command with the arguments `--archive-cluster-state=true` and `--archive-path=`: From 4564277334a22a8f76a5f030588a527463f94c19 Mon Sep 17 00:00:00 2001 From: Natalia Ivakina <82437520+NataliaIvakina@users.noreply.github.com> Date: Fri, 5 Sep 2025 14:23:27 +0200 Subject: [PATCH 2/2] Apply suggestions from code review --- .../ROOT/pages/clustering/clustering-advanced/unbind.adoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc b/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc index 30f18b62a..0a72ee3b3 100644 --- a/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc +++ b/modules/ROOT/pages/clustering/clustering-advanced/unbind.adoc @@ -12,9 +12,11 @@ Therefore, it is strongly recommended to consult with Neo4j Support before using Use the `unbind` command only when troubleshooting **a specific server** and remember there is no guarantee that the allocator will reassign the same databases to this server, potentially resulting in orphaned database stores. -The `unbind` command preserves all database stores on the server; and when the unbound server is restarted, it is seen as an entirely new server - so it won't host any of the database it did host before the operation. +The `unbind` command preserves all database stores on the server; and when the unbound server is restarted, it is seen as an entirely new server. +Therefore, it will not host any of the databases it hosted before the operation. -The `unbind` command can't be used anymore to convert a cluster member into a standalone server. For that we recommend taking backups, create the standalone server and the use those backups to create the databases. +In 2025.x, the `unbind` command cannot be used to convert a cluster member into a standalone server. +Instead, it is recommended to take backups, create the standalone server, and then use those backups to restore the databases. ==== [[unbind-command-syntax]]