CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2357 Commits
44 Branches
214 Tags
188 MiB
 
 
Tag: Branch: Tree: 80d1424680
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '80d1424680'
${ noResults }
besu/KNOWN_ISSUES.md

2.4 KiB
Raw Blame History

Known Issues

Details on previously identified known issues are provided below. Details on known issues identfied in the current release are provided in the Changelog.

Known issues are open issues categorized as Very High or High impact.

Eth/65 loses peers

From v1.4.4, eth/65 is disabled by default.

If enabled, peers will slowly drop off and eventually Besu will fall out of sync or stop syncing.

A fix for this issue is being actively worked on.

Fast sync when running Besu on cloud providers

A known RocksDB issue causes fast sync to fail when running Besu on certain cloud providers. The following error is displayed repeatedly:

...
EthScheduler-Services-1 (importBlock) | ERROR | PipelineChainDownloader | Chain download failed. Restarting after short delay.
java.util.concurrent.CompletionException: org.hyperledger.besu.plugin.services.exception.StorageException: org.rocksdb.RocksDBException: block checksum mismatch:
....

This behaviour has been seen on AWS and Digital Ocean.

Workaround -> On AWS, a full restart of the AWS VM is required to restart the fast sync.

Fast sync is not currently supported on Digital Ocean. We are investigating options to add support for fast sync on Digital Ocean.

Privacy users with private transactions created using v1.3.4 or earlier

A critical issue for privacy users with private transactions created using Hyperledger Besu v1.3.4 or earlier has been identified. If you have a network with private transaction created using v1.3.4 or earlier, please read the following and take the appropriate steps: https://wiki.hyperledger.org/display/BESU/Critical+Issue+for+Privacy+Users

Changes not saved to database correctly causing inconsistent private states

While running reorg testing on Besu and Orion, inconsistent private states were observed in some long running tests when state changes were not saved to the database correctly when executing the private transaction.

Workaround -> As the private transaction payloads have all been distributed and the privacy marker transactions included in the chain, resynchronizing the node with an inconsistent state will re-execute the private transactions.

A fix for this issue is being actively worked on.