Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DAG and EtHash cache to not get corrupted on interruption, or crash, or powerdown #874

Closed
AlexeyAkhunov opened this issue Aug 5, 2020 · 0 comments · Fixed by #944
Closed

DAG and EtHash cache to not get corrupted on interruption, or crash, or powerdown #874

AlexeyAkhunov opened this issue Aug 5, 2020 · 0 comments · Fixed by #944
Assignees
@mandrigin

Comments

@AlexeyAkhunov
Copy link
Contributor

Currently we may get this sort of error if DAG or EtHash cache gets corrupted:

ERROR[08-05|11:30:00.088] Invalid header encountered               number=3299905 hash="ae4250…f985b7" err="invalid mix digest"
WARN [08-05|11:30:00.088] Synchronisation failed, dropping peer    peer=b7a16e347add8061 err="retrieved hash chain is invalid: invalid mix digest"
WARN [08-05|11:30:00.371] Head headers broke chain ordering        peer=24dd0114a854c059 index=0 requested=10598770 received=3307585
WARN [08-05|11:30:00.371] Synchronisation failed, dropping peer    peer=24dd0114a854c059 err="retrieved hash chain is invalid: head headers broke chain ordering"
INFO [08-05|11:30:05.375] Staged sync finished

The workaround is to remove DAG and EtHash cache directories and restart.

We need to make DAG and EtHash files atomic and consistent, so that we do not need the workaround. Perhaps, use a separate LMDB file to store them?
@mandrigin mandrigin self-assigned this Aug 19, 2020
@mandrigin mandrigin mentioned this issue Aug 20, 2020
Merged
battlmonstr pushed a commit that referenced this issue Sep 14, 2023
@yperbasis
Revert "Revert "little additions to chain/chain_config to support eip… (
5b32270 
#874)

…-4844" (#872)"

Restore PR #848 since `shardingForkTime` is useful for compatibility
with EIP-4844-devnet-4.
cffls pushed a commit to cffls/erigon that referenced this issue Aug 1, 2024
@praetoriansentry @V-Staykov
fix: broken kurtosis CI dependency (erigontech#874)
9733d9a 
The current workflow expects the
`templates/cdk-erigon/config-sequencer.yaml` file. This file has been
removed and consolidated. The command that it's running shouldn't be
needed anymore since we removed `zkevm.sequencer-initial-fork-id` from
the file already.

Co-authored-by: Valentin Staykov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mandrigin mandrigin

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Never store Ethash caches to disk erigontech/erigon
2 participants
@mandrigin @AlexeyAkhunov