Skip to content
Merged
Changes from all commits
Commits
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
7 changes: 6 additions & 1 deletion modules/ROOT/pages/clustering/setup/discovery.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Neo4j provides several mechanisms for cluster members to discover each other and
In Neo4j 5.23, a new discovery service was introduced.
You must move to the new version before you start using Neo4j 2025.01.

See link:https://neo4j.com/docs/operations-manual/5/clustering/setup/discovery/[the guide for the Neo4j 5.x series] for more information.
Details are provided in link:https://neo4j.com/docs/operations-manual/5/clustering/setup/discovery/#clustering-discovery-v1-to-v2[the guide for the Neo4j 5.x series].
====

[[clustering-discovery-methods]]
Expand All @@ -23,6 +23,11 @@ See link:https://neo4j.com/docs/operations-manual/5/clustering/setup/discovery/[
Depending on the type of xref:configuration/configuration-settings.adoc#config_dbms.cluster.discovery.resolver_type[`dbms.cluster.discovery.resolver_type`] currently in use, the discovery service can use a list of server addresses, DNS records, or Kubernetes services to discover other servers in the cluster.
The discovery configuration is used for initial discovery and to continuously exchange information about changes to the topology of the cluster.

[NOTE]
====
Regardless of the method used to resolve the list of server addresses, ensure that the endpoint for each server hosting the `system` database in primary mode is included.
====

[[clustering-discovery-list]]
=== Discovery using a list of server addresses

Expand Down
Loading