vacp2p/status-linea-besu
1
0
Fork 0
mirror of https://github.com/vacp2p/status-linea-besu.git synced 2026-01-08 21:38:15 -05:00
Code Issues Packages Projects Releases Wiki Activity

Updated known issues for 1.4.6 (#996)

Browse Source 
* Updated known issues

Signed-off-by: Madeline <madeline.murray@consensys.net>
This commit is contained in:
MadelineMurray
2020-05-29 08:16:44 +10:00
committed by GitHub
parent 2e8831a07a
commit 3fa0bbfc05
2 changed files with 23 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
KNOWN_ISSUES.md
View File

@@ -5,15 +5,19 @@ in the current release are provided in the [Changelog](CHANGELOG.md).
Known issues are open issues categorized as [Very High or High impact](https://wiki.hyperledger.org/display/BESU/Defect+Prioritisation+Policy).
## Eth/65 not backwards compatible
## Scope of logs query causing Besu to hang
[`eth_getLogs` queries that are too large or too broad can cause Besu to never return](https://github.com/hyperledger/besu/issues/944).
Workaround - Limit the number of blocks queried by each `eth_getLogs` call.
A fix for this issue is being actively worked on.
## Eth/65 loses peers
From v1.4.4, `eth/65` is [disabled by default](https://github.com/hyperledger/besu/pull/741).
The `eth/65` change is not [backwards compatible](https://github.com/hyperledger/besu/issues/723).
This has the following impact:
* In a private network, nodes using the 1.4.3 client cannot interact with nodes using 1.4.2 or earlier
clients.
* On mainnet, synchronizing eventually stalls.
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.
@@ -36,12 +40,6 @@ Workaround -> On AWS, a full restart of the AWS VM is required to restart the fa
Fast sync is not currently supported on Digital Ocean. We are investigating options to
[add support for fast sync on Digital Ocean](https://github.com/hyperledger/besu/issues/591).
## Bootnodes must be validators when using onchain permissioning
- Onchain permissioning nodes can't peer when using a non-validator bootnode [\#528](https://github.com/hyperledger/besu/issues/528)
Workaround -> When using onchain permissioning, ensure bootnodes are also validators.
## 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