You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/clustering/databases.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -235,7 +235,7 @@ Neo4j 5.24 introduces the xref:reference/procedures.adoc#procedure_dbms_cluster_
235
235
236
236
* To make your database write-available again after it has been lost (for example, due to a disaster).
237
237
// See xref:clustering/disaster-recovery.adoc[] for more information.
238
-
238
+
239
239
[CAUTION]
240
240
====
241
241
The recreate procedure works only for real user databases and not for composite databases, or the `system` database.
@@ -304,7 +304,7 @@ If not used stores were more up to date than the used ones, this results in data
304
304
305
305
You can specify a set of available servers.
306
306
The stores on all allocations will be synchronized to the most up-to-date store from the defined servers.
307
-
The number of defined servers cannot exceed the number of total allocations in the desired topology.
307
+
The number of defined servers cannot exceed the number of total allocations in the desired topology.
308
308
309
309
[source, shell]
310
310
----
@@ -341,7 +341,7 @@ There is an option to define a new topology when recreating a database.
341
341
This can be beneficial during a disaster, if enough servers are not available to recreate the database with the original topology.
342
342
When altering the total number of allocations down during a recreation, it is important to remember that the number of seeding servers cannot exceed the number of total allocations of the database.
343
343
This also holds true when using recreate with an empty list of seeders.
344
-
If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail.
344
+
If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail.
345
345
346
346
[source, shell]
347
347
----
@@ -488,7 +488,7 @@ Each configuration value is specified as a name followed by `=` and the value, a
0 commit comments