Skip to content

You should list system primaries in your endpoints #2016

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 4 commits into from
Jan 9, 2025
Merged

You should list system primaries in your endpoints #2016

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8a9b1f8
your endpoints should include the system database primaries
jackwaudby Dec 18, 2024
2e52ee4
new lines
jackwaudby Dec 18, 2024
676ae97
Update configuration-settings.adoc
NataliaIvakina Jan 8, 2025
5f83ad2
Update modules/ROOT/pages/clustering/setup/discovery.adoc
NataliaIvakina Jan 9, 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
5 changes: 5 additions & 0 deletions modules/ROOT/pages/clustering/setup/discovery.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,11 @@ The following sections describe the different methods for server discovery, conf
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
8 changes: 6 additions & 2 deletions modules/ROOT/pages/configuration/configuration-settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -365,7 +365,6 @@ m|+++10m+++
|===
|Description
a|A comma-separated list of endpoints that a server should contact in order to discover other cluster members.
Typically, all cluster members, including the current server, must be specified in this list.
The setting configures the endpoints for Discovery service V1.
|Valid values
a|A comma-separated list where each element is a socket address in the format of `hostname:port`, `hostname`, or `:port`.
Expand All @@ -382,14 +381,19 @@ m|
|===
|Description
a|A comma-separated list of endpoints that a server should contact in order to discover other cluster members.
Typically, all cluster members, including the current server, must be specified in this list.
The setting configures the endpoints for Discovery service V2.
|Valid values
a|A comma-separated list where each element is a socket address in the format of `hostname:port`, `hostname`, or `:port`.
|Default value
m|
|===

[NOTE]
====
`dbms.cluster.discovery.endpoints` and `dbms.cluster.discovery.v2.endpoints` must contain all cluster members hosting a `system` database in primary mode.
However, it is typical that all cluster members, including the current server, are specified in those lists.
====

[role=label--enterprise-edition label--new-5.22 label--deprecated-5.26]
[[config_dbms.cluster.discovery.version]]
=== `dbms.cluster.discovery.version`
Expand Down
Loading