Skip to content

Commit f99338e

Browse files
author
Frannie-Ludmilla
committed
Sync with monorepo definitions
1 parent 1b1b7e7 commit f99338e

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

modules/ROOT/pages/procedures.adoc

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1090,21 +1090,22 @@ The deprecated `dbms.quarantineDatabase()` procedure is available in Cypher 5, b
10901090
.Details
10911091
|===
10921092
| *Syntax* 3+m| dbms.unquarantineDatabase(server, databaseName, operation) :: ()
1093-
| *Description* 3+a| Remove the quarantine status from a database in a server performing a cleanup `operation`.
1094-
The possible values for the cleanup operation are:
1095-
1096-
* `keepStateKeepStore` -- do nothing; leave store and cluster state as they are.
1097-
* `replaceStateKeepStore` -- join as a new member, clearing the current cluster state but keeping the store.
1098-
* `replaceStateReplaceStore` -- join as a new member, clearing both the current cluster state and the store.
1093+
| *Description* 3+a| Lift quarantine from a database on a given server.
10991094
.4+| *Input arguments* | *Name* | *Type* | *Description*
1100-
| `server` | `STRING` | The name or the id of the server where there is the quarantined database.
1101-
| `databaseName` | `STRING` | The name of the database whose quarantine status must be removed.
1102-
| `operation` | `STRING` | Select a cleanup operation to perform while removing the quarantine.
1095+
| `server` | `STRING` | The identifier of the server where the quarantine for database will be lifted.
1096+
| `databaseName` | `STRING` | The name of the database for the quarantine will be lifted.
1097+
| `operation` | `STRING` | Optional operation to apply while lifting the quarantine.
11031098
| *Mode* 3+| DBMS
11041099
|===
11051100

11061101
[NOTE]
11071102
====
1103+
The possible values for the optional operation are:
1104+
1105+
* `keepStateKeepStore` -- do nothing; leave store and cluster state as they are.
1106+
* `replaceStateKeepStore` -- join as a new member, clearing the current cluster state but keeping the store.
1107+
* `replaceStateReplaceStore` -- join as a new member, clearing both the current cluster state and the store.
1108+
11081109
If you choose to clear the current cluster state, the server will try to join as a new member,
11091110
but this joining can succeed if and only if there is a majority of old members "letting" the new members in.
11101111
Let's assume our cluster has a topology with three primaries.

0 commit comments

Comments
 (0)