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/scalability/sharded-property-databases/admin-operations.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ Failure to meet this requirement will make a given replica of a property shard u
130
130
If a property shard replica does fall behind the transaction log range available on the graph shard, you can recover it by:
131
131
132
132
. Connecting to the `system` database on the server hosting the affected replica using the _bolt://_ scheme.
133
-
//. Quarantining the replica using xref:procedures.adoc#procedure_dbms_quarantineDatabase[`dbms.quarantineDatabase()`].
133
+
. Quarantining the replica using xref:procedures.adoc#procedure_dbms_quarantineDatabase[`dbms.quarantineDatabase()`].
134
134
. Unquarantining the replica using xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`dbms.unquarantineDatabase()`] with the `replaceStateReplaceStore` option.
135
135
This will force the replica to copy the database store files from another replica of the property shard.
0 commit comments