mirrors/scylladb
1
0
Fork 0
mirror of https://github.com/scylladb/scylladb.git synced 2026-05-12 19:02:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: link general repairs page to RBNO page

Browse Source 
Information was duplicated before and the version on this page was outdated - RBNO is enabled for replace operation already.

Closes #12984
This commit is contained in:
Marcin Maliszkiewicz
2023-02-24 13:04:43 +01:00
committed by Botond Dénes
parent 991379bdb3
commit bd7caefccf
1 changed files with 1 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/operating-scylla/procedures/maintenance/repair.rst
View File

@@ -15,6 +15,7 @@ As long as the cluster can satisfy the required consistency level (usually quoru
* :doc:`Hinted Handoff </architecture/anti-entropy/hinted-handoff>`
* :doc:`Read Repair </architecture/anti-entropy/read-repair>`
* :doc:`Repair Based Node Operations </operating-scylla/procedures/cluster-management/repair-based-node-operation>`
* Repair - described in the following sections
Repair Overview
@@ -50,30 +51,6 @@ Row-level repair improves Scylla in two ways:
* keeping the data in a temporary buffer.
* using the cached data to calculate the checksum and send it to the replicas.
Repair Base Operation
---------------------
.. versionadded:: 4.0 Scylla Open Source (disabled)
ScyllaDB has two mechanisms to synchronize data between nodes:
* Streaming - used for cluster topology changes, such as adding or removing nodes.
* Row Level Repair - an offline process that compares and syncs data between nodes .
With *Repair Base Operation*, Scylla uses row-level repair as the unified underlying mechanism for repair operation **and** all node operations, e.g., bootstrap, decommission, remove node, replace node, rebuild node.
This safer process makes the node operations resumable, syncing only the inconsistent data.
Also, replaced nodes now accept writes, which means there is no longer a need to repair after replacing a node.
**This feature is disabled by default.**
You can enable or disable this feature with a configuration parameter in the *scylla.yaml*:
.. code-block:: none
enable_repair_based_node_ops: [true|false]
See also
* `Scylla Manager documentation <https://manager.docs.scylladb.com/>`_