initial.server.mode_constraint
|
This setting constrains the operating mode of the database to be used only in primary or secondary mode.
Default setting is NONE, ie. no constraint.
As an initial setting, the value set here is used when a server is first enabled.
Once enabled, a server’s mode constraint can only be changed with ALTER SERVER 'name' SET OPTIONS {modeConstraint:'PRIMARY'}.
Example: a server configured with initial.server.mode_constraint=SECONDARY is only allocated databases whose topologies contain 1 or more secondary.
This server always only hosts those databases in SECONDARY mode.
|
initial.dbms.automatically_enable_free_servers
|
|
server.cluster.system_database_mode
|
Every cluster member hosts the system database.
This config controls what mode a given instance hosts the system database in: PRIMARY or SECONDARY.
Example: server.cluster.system_database_mode=SECONDARY means that this instance holds only a secondary copy of the system database.
|
|
There should be a relatively high number (5-7) of system primaries, spread across availability zones.
However, if enabling more than 10 servers, it is recommended to start making the later ones secondaries.
|
|
dbms.cluster.minimum_initial_system_primaries_count
|
Minimum number of servers configured with server.cluster.system_database_mode=PRIMARY required to form a cluster.
Example: dbms.cluster.minimum_initial_system_primaries_count=3 specifies that the cluster is considered bootstrapped and the DBMS online when at least 3 system database primaries have discovered one another.
|
dbms.cluster.discovery.resolver_type
|
This setting specifies the strategy that the instance uses to determine the addresses for other instances in the cluster to contact for bootstrapping.
Possible values are:
LIST-
Treats dbms.cluster.endpoints as a list of addresses of servers to contact for discovery.
DNS-
Treats dbms.cluster.endpoints as a domain name to resolve via DNS.
Expect DNS resolution to provide A records with hostnames or IP addresses of servers to contact for discovery, on the port specified by dbms.cluster.endpoints.
SRV-
Treats dbms.cluster.endpoints as a domain name to resolve via DNS.
Expect DNS resolution to provide SRV records with hostnames or IP addresses and ports, of servers to contact for discovery.
K8S-
Accesses the Kubernetes list service API to derive addresses of servers to contact for discovery.
Requires dbms.kubernetes.label_selector to be a Kubernetes label selector for Kubernetes services running a server each and dbms.kubernetes.discovery.service_port_name to be a service port name identifying the discovery port of cluster servers services.
The value of dbms.cluster.endpoints is ignored for this option.
For more details, see Discovery in Kubernetes.
You need to set dbms.cluster.endpoints in the neo4j.conf file.
Detailed information about discovery and discovery configuration options is given in Methods for server discovery.
|
dbms.cluster.endpoints Renamed in 2025.01
|
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.
Example: dbms.cluster.discovery.resolver_type=LIST combined with server01.example.com:6000,server02.example.com:6000,server03.example.com:6000 attempt to reach Neo4j instances listening on server01.example.com, server02.example.com and server03.example.com; all on port 6000.
|
server.cluster.raft.advertised_address
|
The address/port setting that specifies where the Neo4j server advertises to other members of the cluster that it listens for Raft messages within the cluster.
Example: server.cluster.raft.advertised_address=192.168.33.20:7000 listens for cluster communication in the network interface bound to 192.168.33.20 on port 7000.
|
server.cluster.advertised_address
|
The address/port setting that specifies where the instance advertises it listens for requests for transactions in the transaction-shipping catch-up protocol.
Example: causal_clustering.transaction_advertised_address=192.168.33.20:6001 listens for transactions from cluster members on the network interface bound to 192.168.33.20 on port 6001.
|
server.cluster.raft.listen_address
|
The address/port setting that specifies which network interface and port the Neo4j instance binds to for cluster communication.
This setting must be set in coordination with the address this instance advertises it listens at in the setting server.cluster.raft.advertised_address.
Example: server.cluster.raft.listen_address=0.0.0.0:7000 listens for cluster communication on any network interface at port 7000.
|
server.cluster.listen_address
|
The address/port setting that specifies which network interface and port the Neo4j instance binds to for cluster communication.
This setting must be set in coordination with the address this instance advertises it listens at in the setting server.cluster.advertised_address.
Example: server.cluster.listen_address=0.0.0.0:6001 listens for cluster communication on any network interface at port 6001.
|