Skip to content

Commit c04a9dd

Browse files
committed
Force recovery docs
1 parent e04d5b4 commit c04a9dd

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

doc/reference/tarantool_cli_options.rst

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,25 @@ Options
6565

6666
Start an external coordinator used for a :ref:`supervised failover <repl_supervised_failover>`.
6767

68+
.. _tarantool_cli_force_recovery:
69+
70+
.. option:: --force-recovery
71+
72+
**Since:** :doc:`3.0.0 </release/3.0.0>`.
73+
74+
Try to continue if there is an error while reading a corrupted snapshot or write-ahead log file during the :ref:`recovery process <internals-recovery_process>`:
75+
76+
- For a corrupted :ref:`snapshot file <index-box_persistence>` -- at instance start.
77+
- For a corrupted :ref:`write-ahead log file <internals-wal>` -- at instance start or when applying an update at a replica.
78+
79+
With this option enabled, Tarantool skips invalid records, reads as much data as possible and lets the process finish with a warning.
80+
Then call :ref:`box.snapshot() <box-snapshot>` to make a new snapshot so that the corrupted snapshots or write-ahead logs aren't used for recovery anymore.
81+
82+
You can also enable this option using the ``TT_FORCE_RECOVERY`` environment variable.
83+
``TT_FORCE_RECOVERY`` has a lower priority than the ``--force-recovery`` option.
84+
85+
Example on GitHub: `force_recovery <https://github.com/tarantool/doc/tree/latest/doc/code_snippets/snippets/config/instances.enabled/force_recovery>`_
86+
6887
.. _index-tarantool_version:
6988

7089
.. option:: -v, -V, --version

0 commit comments

Comments
 (0)