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 Oct 24, 2023

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

In a clustered environment, `CALL dbms.setConfigValue` affects only the server it is run against, and it is not propagated to other members.
If you want to change the configuration settings on all cluster members, you have to run the procedure against each of them and update their _neo4j.conf_ file.
Each member of the cluster has its own _neo4j.conf_ file and thus, it is possible that the settings for the same database could be different on different members of the cluster.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd maybe switch this up slightly and say "Each member of the cluster has its own neo4j.conf file, but it is not recommended for settings for the same database to be different across members of the cluster. As this can have unforeseen consequences."

@AlexicaWright AlexicaWright merged commit 00cd0a6 into neo4j:dev Oct 25, 2023
AlexicaWright added a commit to AlexicaWright/docs-operations that referenced this pull request Oct 25, 2023
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