From 72a9e13d6f30fdb8250d8aff5d60e9037845915d Mon Sep 17 00:00:00 2001 From: Ruaridh Date: Mon, 8 Jun 2020 14:49:16 +0100 Subject: [PATCH] fix pruning section (#564) --- contrib/kava-3/migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/kava-3/migration.md b/contrib/kava-3/migration.md index f1ce4311..10fd4fef 100644 --- a/contrib/kava-3/migration.md +++ b/contrib/kava-3/migration.md @@ -18,7 +18,7 @@ The riskiest thing a validator can do is discover that they made a mistake and r ### Pruning -kava-3 uses tendermint version 0.33. Recent testing in Game of Zones and Kava has shown that nodes which are running with the default or custom pruning strategy have a [memory leak](https://github.com/tendermint/iavl/issues/256) that can cause nodes to crash and lead to irrecoverable data loss. Until a patch is released, the __ONLY__ pruning strategies that are safe to run are `everything` (an archival node) or `nothing` (only the most recent state is kept). It is __strongly__ recommended that validators use `pruning="everything"` for kava-3. +kava-3 uses tendermint version 0.33. Recent testing in Game of Zones and Kava has shown that nodes which are running with the default or custom pruning strategy have a [memory leak](https://github.com/tendermint/iavl/issues/256) that can cause nodes to crash and lead to irrecoverable data loss. Until a patch is released, the __ONLY__ pruning strategies that are safe to run are `nothing` (an archival node, where nothing is deleted) or `everything` (only the most recent state is kept). It is __strongly__ recommended that validators use `pruning="nothing"` for kava-3. The pruning config is set in $HOME/.kvd/config/app.toml. Example safe configurations are: