You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/clustering/databases.adoc
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,11 @@
4
4
[[database-management]]
5
5
= Managing databases in a cluster
6
6
7
-
The number of both primary and secondary servers to host a database can be set when the database is created and altered after creation.
8
-
The command `CREATE DATABASE` can be used to specify the initial topology and `ALTER DATABASE` can be used to change the topology once the database is created.
7
+
When creating a database or altering it after creation, you can specify its role: `PRIMARY` or `SECONDARY`.
8
+
To specify the initial topology, use the command `CREATE DATABASE`.
9
+
To change the topology once the database is created, run the `ALTER DATABASE` command.
10
+
Note that the database role must be aligned with the server's xref:clustering/servers.adoc#server-enabled-state[`modeConstraint`], which value can be `PRIMARY`, or `SECONDARY`, or `NONE`.
11
+
9
12
If a database is no longer needed, the command `DROP DATABASE` deletes the database from the cluster.
10
13
11
14
[[cluster-system-db]]
@@ -15,7 +18,8 @@ The `system` database contains metadata on the DBMS and security configuration.
15
18
When connected to this database you can only perform a specific set of administrative tasks, such as managing databases, servers, and access control.
16
19
17
20
In the clustered environment, the `system` database can be in a primary or secondary mode.
18
-
To configure its mode, use the xref:configuration/configuration-settings.adoc#config_server.cluster.system_database_mode[`server.cluster.system_database_mode`] setting.
21
+
To configure its mode, use the xref:configuration/configuration-settings.adoc#config_server.cluster.system_database_mode[`server.cluster.system_database_mode`] setting in the _neo4j.conf_ file.
22
+
This has to be done before starting the Neo4j process.
19
23
20
24
Deploying a cluster for the first time, consider configuring the xref:configuration/configuration-settings.adoc#config_dbms.cluster.minimum_initial_system_primaries_count[`dbms.cluster.minimum_initial_system_primaries_count`].
21
25
This setting defaults to `3`.
@@ -61,7 +65,7 @@ For example, if the cluster's servers are set up with mode constraints to contai
61
65
[NOTE]
62
66
====
63
67
If `TOPOLOGY` is not specified, the database is created according to `initial.dbms.default_primaries_count` and `initial.dbms.default_secondaries_count` specified in _neo4j.conf_.
64
-
After cluster startup, you can overwrite these values using the `dbms.setDefaultAllocationNumbers` procedure.
68
+
After cluster startup, you can overwrite these values using the `dbms.setDefaultAllocationNumbers()` procedure.
Copy file name to clipboardExpand all lines: modules/ROOT/pages/clustering/server-syntax.adoc
+49-31Lines changed: 49 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,23 @@
1
1
:description: This section provides a summary of server management Cypher syntax.
2
2
[role=enterprise-edition]
3
3
[[server-commands-reference]]
4
-
= Server commands reference
4
+
= Server management command syntax
5
5
6
-
Servers can be added and managed using a set of Cypher administration commands executed against the `system` database.
6
+
Servers can be added and managed using a set of Cypher administrative commands executed against the `system` database.
7
7
8
-
When connected to the DBMS over `bolt`, administration commands are automatically routed to the `system` database.
8
+
When connected to the DBMS over `bolt`, administrative commands are automatically routed to the `system` database.
9
9
10
10
11
11
[[server-management-syntax]]
12
12
== Server management command syntax
13
13
14
14
[NOTE]
15
15
====
16
-
More details about the syntax descriptions can be found xref:database-administration/syntax.adoc[here].
16
+
More details about the syntax descriptions can be found on the page xref:database-administration/syntax.adoc#administration-syntax-reading[Database management command syntax -> Reading the administrative commands syntax].
17
17
====
18
18
19
+
=== Enable a server
20
+
19
21
[cols="<15s,<85"]
20
22
|===
21
23
| Command
@@ -38,73 +40,86 @@ a| `GRANT SERVER MANAGEMENT`
38
40
(see xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-privilege-management[SERVER MANAGEMENT privileges])
39
41
|===
40
42
43
+
44
+
=== List servers
45
+
41
46
[cols="<15s,<85"]
42
47
|===
43
48
| Command
44
-
m| ALTER SERVER
49
+
m| SHOW SERVERS
45
50
46
51
| Syntax
47
52
a|
48
53
[source, syntax, role=noheader]
49
54
----
50
-
ALTER SERVER 'name' SET OPTIONS "{" option: value[,...] "}"
0 commit comments