Skip to content

Commit

Permalink
clarify topology
Browse files Browse the repository at this point in the history
  • Loading branch information
AlexicaWright committed Jan 8, 2024
1 parent 0df6421 commit 8e3e737
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions modules/ROOT/pages/clustering/databases.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -172,8 +172,9 @@ SHOW SERVERS YIELD serverId, name, address, state, health, hosting;
In this case, the address for `server01` is `localhost:7687` and thus, the server ID is `8512c9b9-d9e8-48e6-b037-b15b0004ca18`.
+
. On one of the servers, use the `system` database and create the database `foo` using the server ID of `server01`.
If you know how your restored database should be allocated across the cluster, you can specify the desired topology in the `CREATE DATABASE` command.
If you don't specify a topology, the database is allocated according to what is specified in the _neo4j.conf_ file.
The topology of `foo` is stored in the `system` database and when you create it, it is allocated according to what is specified in the _neo4j.conf_ file.
This may be different from the topology of `foo` when it was backed up.
If you want to ensure a certain allocation across the cluster, you can specify the desired topology in the `CREATE DATABASE` command.
See <<#_create_database, `CREATE DATABASE`>> for more information.
+
[source, cypher, role=noplay]
Expand Down

0 comments on commit 8e3e737

Please sign in to comment.