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/database-administration/standard-databases/errors.adoc
+8-13Lines changed: 8 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,26 +162,26 @@ It produces a database dump that can be further examined and potentially repaire
162
162
163
163
When a database encounters a severe error during its normal run, which prevents it from a further operation, Neo4j stops that database and brings it into a `quarantined` state.
164
164
Meaning, it is not possible to restart it with a simple `START DATABASE` command.
165
-
You have to execute `CALL dbms.unquarantineDatabase(server, databaseName, operation)` in order to lift the quarantine, specifying as `server` the instance with the failing database.
165
+
You have to run `CALL dbms.unquarantineDatabase(server, database, operation)` to lift the quarantine, specifying as `server` the instance with the failing database.
166
+
167
+
The `dbms.unquarantineDatabase()` procedure is introduced in Neo4j 2025.01 to replace the now-deprecated xref:procedures.adoc#procedure_dbms_quarantineDatabase[`dbms.quarantineDatabase`()].
166
168
167
169
After lifting the quarantine, the instance will automatically try to bring the database to the desired state.
| `server` | String | The identifier of the server where the quarantine for database will be lifted.
179
-
| `databaseName` | String | The name of the database that will be put into or removed from quarantine.
181
+
| `database` | String | The name of the database that will be put into or removed from quarantine.
180
182
| `operation` | String | Optional operation to apply while lifting the quarantine.
181
183
|===
182
184
183
-
[NOTE]
184
-
====
185
185
The possible values for the optional operation are:
186
186
187
187
* `keepStateKeepStore` -- do nothing; leave store and cluster state as they are.
@@ -193,16 +193,11 @@ but this joining can succeed if and only if there is a majority of old members "
193
193
Let's assume our cluster has a topology with three primaries.
194
194
If there is only one server in `QUARANTINED` mode, then it is safe to choose `replaceStateKeepStore` or `replaceStateReplaceStore`.
195
195
If there are two servers in `QUARANTINED` mode, then you should not use concurrently `replaceStateKeepStore` or `replaceStateReplaceStore` for both servers because there would be no majority to let them in.
196
-
====
197
196
198
-
*Returns:*
197
+
*Return arguments:*
199
198
200
199
The procedure doesn't return any value.
201
200
202
-
[NOTE]
203
-
====
204
-
The `dbms.unquarantineDatabase` procedure replaces xref:procedures.adoc#procedure_dbms_quarantineDatabase[`dbms.quarantineDatabase`], which has been deprecated in Neo4j 5.26.
205
-
====
206
201
207
202
.Check if a database is quarantined
208
203
[source, cypher]
@@ -226,7 +221,7 @@ neo4j@system> SHOW DATABASE foo;
226
221
====
227
222
A `quarantined` state is persisted for user databases.
228
223
This means that if a database is quarantined, it will remain so even if that Neo4j instance is restarted.
229
-
You can remove it only by running the xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`dbms.unquarantineDatabase`] procedure.
224
+
You can remove it only by running the xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`dbms.unquarantineDatabase()`] procedure.
230
225
231
226
The one exception to this rule is for the built-in `system` database.
232
227
Any quarantine for that database is removed automatically after instance restart.
0 commit comments