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

Added more information on onchain privacy group breaking change and updated known issue (#1328)

Browse Source 
* Added more information on breaking change and updated known issue

Signed-off-by: Madeline <madeline.murray@consensys.net>

* Added workaround

Signed-off-by: Madeline <madeline.murray@consensys.net>
This commit is contained in:
MadelineMurray
2020-08-25 22:40:19 +10:00
committed by GitHub
parent 47777e2049
commit fdf7521384
2 changed files with 18 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
KNOWN_ISSUES.md
View File

@@ -55,10 +55,13 @@ Workaround -> Do not use permissioning with Kubernetes.
A fix for this issue is being actively worked on.
## Restart caused by insufficient memory can cause inconsistent private state
## Changes not saved to database correctly causing inconsistent private states
While running reorg testing on Besu and Orion, insufficient memory caused Besu to restart, resulting in the state on that machine to become inconsistent with the rest of the members of the privacy group.
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 -> Ensure you allocate enough memory for the Java Runtime Environment that the node does not run out of memory.
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.