Skip to content

Conversation

@AlexicaWright
Copy link
Contributor

No description provided.

@neo-technology-commit-status-publisher
Copy link
Collaborator

neo-technology-commit-status-publisher commented Jan 8, 2024

This PR includes documentation updates.

You can view the updated docs at https://neo4j-docs-operations-1313.surge.sh

. 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope

The values from the neo4j.conf file are taken once when the system database created / when the dbms is created and then written to the system database. Later on it does not matter at all what is written into the config file.

The topology of foo is stored in the system database and when you create it, it is allocated according what was specified in the TOPOLOGY clause, of if not specified what the default topology is set to. The default topology is stored in the system database, and can be shown with CALL dbms.showTopologyGraphConfig.

@AlexicaWright AlexicaWright merged commit 46f6653 into neo4j:dev Jan 8, 2024
AlexicaWright added a commit to AlexicaWright/docs-operations that referenced this pull request Jan 8, 2024
AlexicaWright added a commit that referenced this pull request Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants