Skip to content
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

Remove deleted discovery procedures #1991

Merged
merged 1 commit into from
Dec 16, 2024
+0 −49
Merged

Remove deleted discovery procedures #1991

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
49 changes: 0 additions & 49 deletions modules/ROOT/pages/procedures.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -334,18 +334,6 @@ Since Neo4j 5.23, it can be run with the `SERVER MANAGEMENT` privilege.
It will still run with the `Admin` privilege, but that should be considered deprecated.
====

[role=label--enterprise-edition label--new-5.26 label--admin-only ]
[[procedure_dbms_cluster_movetonextdiscoveryversion]]
=== dbms.cluster.moveToNextDiscoveryVersion()

.Details
|===
| *Syntax* 3+m| dbms.cluster.moveToNextDiscoveryVersion()
| *Description* 3+a| The procedure triggers a switch to the next discovery service version for all known members of the cluster (as listed in the system database and discovery).
For example, if the current member's discovery version is V1_ONLY, it will switch all members to V1_OVER_V2. In case of failure, the user must manually resolve the issue.
| *Mode* 3+| DBMS
|===

[role=label--enterprise-edition label--new-5.23]
[[procedure_dbms_cluster_deallocateDatabaseFromServer]]
=== dbms.cluster.deallocateDatabaseFromServer()
Expand Down Expand Up @@ -638,23 +626,6 @@ Since Neo4j 5.23, it can be run with the `SERVER MANAGEMENT` privilege.
It will still run with the `Admin` privilege, but that should be considered deprecated.
====

[role=label--enterprise-edition label--new-5.22 label--admin-only ]
[[procedure_dbms_cluster_showparalleldiscoverystate]]
=== dbms.cluster.showParallelDiscoveryState()


.Details
|===
| *Syntax* 3+m| dbms.cluster.showParallelDiscoveryState() :: (mode, stateComparison, v1ServerCount, v2ServerCount)
| *Description* 3+a| Compare the states of Discovery service V1 and Discovery service V2.
.5+| *Return arguments* | *Name* | *Type* | *Description*
| `mode` | `STRING` | mode :: STRING
| `stateComparison` | `STRING` | stateComparison :: STRING
| `v1ServerCount` | `STRING` | v1ServerCount :: STRING
| `v2ServerCount` | `STRING` | v2ServerCount :: STRING
| *Mode* 3+| DBMS
|===


[role=label--enterprise-edition label--new-5.24 label--admin-only]
[[procedure_dbms_cluster_statusCheck]]
Expand Down Expand Up @@ -682,26 +653,6 @@ It will still run with the `Admin` privilege, but that should be considered depr
|===


[role=label--enterprise-edition label--new-5.22 label--admin-only]
[[procedure_dbms_cluster_switchdiscoveryserviceversion]]
=== dbms.cluster.switchDiscoveryServiceVersion()


.Details
|===
| *Syntax* 3+m| dbms.cluster.switchDiscoveryServiceVersion(mode)
| *Description* 3+a| Allows you to select which discovery service should be started.
Possible values are:

* `V1_ONLY` -- it runs only discovery service v1.
* `V1_OVER_V2` -- it runs both Discovery Service V1 and Discovery Service V2, where V1 is the main service and V2 runs in the background.
* `V2_OVER_V1` -- it runs both Discovery Service V1 and Discovery Service V2, where V2 is the main service and V1 runs in the background.
* `V2_ONLY` -- it runs only discovery service v2.
.2+| *Input arguments* | *Name* | *Type* | *Description*
| `mode` | `STRING` | mode :: STRING
| *Mode* 3+| DBMS
|===

[role=label--enterprise-edition label--deprecated-5.23]
[[procedure_dbms_cluster_uncordonServer]]
=== dbms.cluster.uncordonServer()
Expand Down
Loading