Skip to content

Correct inaccuracy about horizontal scaling in Neo4j #2613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 23, 2025
Merged

Correct inaccuracy about horizontal scaling in Neo4j #2613

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
21581a6
Correct inaccuracy about horizontal scaling in Neo4j
NataliaIvakina Sep 22, 2025
4355210
Update modules/ROOT/pages/kubernetes/operations/scaling.adoc
NataliaIvakina Sep 22, 2025
80d8c4c
Apply suggestions from code review
NataliaIvakina Sep 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions modules/ROOT/pages/kubernetes/operations/scaling.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,9 +62,9 @@ helm upgrade <release-name> neo4j/neo4j -f values.yaml
[[horizontal-scaling]]
== Horizontal scaling

You can add a new server to the Neo4j cluster to scale out write or read workloads.
You can add a new server to the Neo4j cluster to scale out read workloads.

The following examples assume that you have a running Neo4j cluster with 3 servers and your Kubernetes cluster has a node available for the new server, `server4`.
The following examples assume that you have a running Neo4j cluster with three servers and your Kubernetes cluster has a node available for the new server, `server4`.

Install `server4` using one of the following options:

Expand Down Expand Up @@ -143,7 +143,7 @@ This feature is useful when you want to add a new server to the cluster and enab
+
[source, shell, subs="attributes"]
----
helm install server4 neo4j --set neo4j.edition=enterprise --set neo4j.acceptLicenseAgreement=yes --set volumes.data.mode=defaultStorageClass --set neo4j.password="password" --set neo4j.minimumClusterSize=3 --set neo4j.name=my-cluster --set neo4j.operations.enableServer=true --set image="neo4j/helm-charts-operations:5.26.0" --set protocol="neo4j"
helm install server4 neo4j --set neo4j.edition=enterprise --set neo4j.acceptLicenseAgreement=yes --set volumes.data.mode=defaultStorageClass --set neo4j.password="password" --set neo4j.minimumClusterSize=3 --set neo4j.name=my-cluster --set neo4j.operations.enableServer=true --set image="neo4j/helm-charts-operations:{neo4j-version-exact}" --set protocol="neo4j"
----

* Use a _values.yaml_ file to set the values for the new server and the _neo4j/neo4j_ Helm chart to install the new server.
Expand Down Expand Up @@ -173,7 +173,7 @@ volumes:

operations:
enableServer: true
image: "neo4j/helm-charts-operations:5.26.0"
image: "neo4j/helm-charts-operations:2025.08"
# protocol can be "neo4j or "neo4j+ssc" or "neo4j+s". Default set to neo4j
# Note: Do not specify bolt protocol here...it will FAIL.
protocol: "neo4j"
Expand Down Expand Up @@ -256,4 +256,5 @@ SHOW DATABASES;
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
----
+
Note that `server4` now hosts the `neo4j` database with the `secondary` role.
Note that `server4` now hosts the `neo4j` database with the `secondary` role.