Skip to content

Commit 00fc473

Browse files
Update warning on how and when to use the unbind command (#2000)
1 parent ffabf0f commit 00fc473

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

modules/ROOT/pages/tools/neo4j-admin/unbind.adoc

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,18 @@
55

66
You can use the `neo4j-admin server unbind` command to remove and archive the cluster state of a cluster server so that it can rebind to a cluster.
77

8+
[WARNING]
9+
====
10+
Due to the new clustering architecture in Neo4j 5.x, the behavior of the `unbind` command has changed significantly compared to Neo4j 4.4.
11+
12+
Running the `unbind` command on any number of servers may result in the loss of cluster quorum, severely affecting clustering functionality.
13+
Therefore, it is strongly recommended to consult with Neo4j Support before using the `unbind` command.
14+
15+
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.
16+
17+
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.
18+
====
19+
820
[[unbind-command-syntax]]
921
== Syntax
1022

@@ -69,14 +81,6 @@ You can use the `neo4j-admin server unbind` command to remove the cluster state
6981
To remove the cluster state of a server, run the `neo4j-admin server unbind` command from the _<NEO4J_HOME>_ folder of that server.
7082
When restarted, an unbound server rejoins the cluster as a new server and has to be enabled using the `ENABLE SERVER` command.
7183

72-
[WARNING]
73-
====
74-
Note that the `unbind` command preserves all database stores on the server.
75-
When the unbound server is restarted and enabled, it is seen as an entirely new server.
76-
Therefore, there is no guarantee that the allocator will pick this server to host the same databases.
77-
This may lead to having orphaned database stores on this server.
78-
====
79-
8084
=== Turn a cluster member into a standalone server
8185

8286
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].

0 commit comments

Comments
 (0)