CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

clarify pruning issue (#886)

Browse Source 
Signed-off-by: Ratan Rai Sur <ratan.r.sur@gmail.com>
pull/889/head
Ratan Rai Sur 5 years ago committed by GitHub
parent 135270605a
commit 5eeba1655d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 4 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 5
      KNOWN_ISSUES.md

5
KNOWN_ISSUES.md
Unescape View File

@ -24,11 +24,10 @@ A fix for this issue is being actively worked on.
## Error full syncing with pruning
- Error syncing with mainnet on Besu 1.3.7 node - MerkleTrieException [\#580](https://github.com/hyperledger/besu/issues/580)
The associated error is `Unable to load trie node value for hash` and is caused by the combination of
full sync and pruning.
The associated error is `Unable to load trie node value for hash`.
Workarounds:
1. Explicitly disable pruning using `--pruning-enabled=false` when using fast sync.
1. Explicitly disable pruning using `--pruning-enabled=false` when using fast sync. It is already disabled by default for full sync.
2. If the `MerkleTrieException` occurs, delete the database and resync.
A fix for this issue is being actively worked on.

Write Preview
Loading…
Cancel
Save