Skip to content

Commit 04c092b

Browse files
Update example for discovery service v1 (#2440)
1 parent 1c220a1 commit 04c092b

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

modules/ROOT/pages/clustering/setup/single-to-cluster.adoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,10 +95,12 @@ Once all servers are enabled, you can scale up user databases using xref:cluster
9595
======
9696
9797
In this example, a standalone server named `server01` is running and two additional servers, `server02` and `server03`, are to be added to form a cluster.
98-
The two additional servers are configured according to xref:clustering/setup/deploy.adoc#cluster-example-configure-a-three-primary-cluster[Configure a cluster with three servers] and are _not_ running.
98+
The two additional servers are configured according to xref:clustering/setup/deploy.adoc#cluster-example-configure-a-three-primary-cluster[Configure a cluster with three servers].
99+
These two new servers should _not_ be started up yet.
99100
Neo4j Enterprise Edition is installed on all three servers.
100101
101-
Start by stopping the standalone server and once it is stopped, edit the xref:configuration/file-locations.adoc[_neo4j.conf_] file to include the discovery endpoints of itself and the servers that will form the cluster.
102+
Start by stopping the standalone server.
103+
Once it is stopped, edit the xref:configuration/file-locations.adoc[_neo4j.conf_] file to include the discovery endpoints of itself and the servers that will form the cluster.
102104
103105
._neo4j.conf_ on server01.example.com:
104106
[source, properties]

0 commit comments

Comments
 (0)