fluencelabs/tendermint
1
0
Fork 0
mirror of https://github.com/fluencelabs/tendermint synced 2025-07-31 04:01:55 +00:00
Code Issues Projects Releases Wiki Activity

explain what to do in case of truncation [ci skip]

Browse Source
This commit is contained in:
Anton Kaliaev
2017-12-15 11:11:21 -06:00
parent 04a18e0a97
commit 4f94caa1b9
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/specification/corruption.rst
View File

@@ -51,7 +51,12 @@ Recovering from data corruption can be hard and time-consuming. Here are two app
./scripts/wal2json/wal2json "$TMHOME/data/cs.wal/wal" > /tmp/corrupted_wal
3. Search for a "CORRUPTED MESSAGE" line.
4. By looking at the previous message and the message after the corrupted one and looking at the logs, try to rebuild the message.
4. By looking at the previous message and the message after the corrupted one
and looking at the logs, try to rebuild the message. If the consequent
messages are marked as corrupted too (this may happen if length header
got corrupted or some writes did not make it to the WAL ~ truncation),
then remove all the lines starting from the corrupted one and restart
Tendermint.
.. code:: bash