From 1679ad57025a1d1a1ee92fbb28cef25bcae36e29 Mon Sep 17 00:00:00 2001 From: Balazs Lendvai <56266523+gfx54b@users.noreply.github.com> Date: Fri, 5 Sep 2025 15:23:07 +0200 Subject: [PATCH 1/2] Remove problematic part from `unbind` docs (#2570) Since 5.0 you cannot use `unbind` to turn a cluster member into a standalone server. --------- Co-authored-by: Natalia Ivakina <82437520+NataliaIvakina@users.noreply.github.com> --- modules/ROOT/pages/tools/neo4j-admin/unbind.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc b/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc index f1fe4a0db..33f04f33a 100644 --- a/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc +++ b/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc @@ -14,7 +14,11 @@ Therefore, it is strongly recommended to consult with Neo4j Support before using In Neo4j 5.x, 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. +Therefore, it will not host any of the databases it hosted before the operation. + +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]] @@ -81,10 +85,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 ee164c627eb12f194e38fd9affe02a78c24fcfbc Mon Sep 17 00:00:00 2001 From: Natalia Ivakina <82437520+NataliaIvakina@users.noreply.github.com> Date: Fri, 5 Sep 2025 15:34:11 +0200 Subject: [PATCH 2/2] Update modules/ROOT/pages/tools/neo4j-admin/unbind.adoc --- modules/ROOT/pages/tools/neo4j-admin/unbind.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc b/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc index 33f04f33a..cd92a2238 100644 --- a/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc +++ b/modules/ROOT/pages/tools/neo4j-admin/unbind.adoc @@ -17,7 +17,7 @@ In Neo4j 5.x, use the `unbind` command only when troubleshooting **a specific se 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. -In 2025.x, the `unbind` command cannot be used to convert a cluster member into a standalone server. +In Neo4j 5.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. ====