lambdaclass / lambdaclass/lambda_ethereum_consensus
Errors while pruning
Open
Nobody has claimed this yet.
bug
P1
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We have recurrent errors in long running sessions related to pruning. This is not affecting the process of transitions states but it's probably affecting DB size. Here is an example log:
[StateDb] Error pruning states: <<70, 97, 105, 108, 101, 100, 32, 116, 111, 32, 115, 116, 97, 114, 116, 32, 105, 116, 101, 114, 97, 116, 111, 114, 32, 102, 111, 114, 32, 116, 97, 98, 108, 101, 32, 115, 116, 97, 116, 101, 100, 98, 95, 98, 108, 111, 99, 107, 95, 114, ...>>
[BlockDb] Error pruning blocks: <<70, 97, 105, 108, 101, 100, 32, 116, 111, 32, 115, 116, 97, 114, 116, 32, 105, 116, 101, 114, 97, 116, 111, 114, 32, 102, 111, 114, 32, 116, 97, 98, 108, 101, 32, 98, 108, 111, 99, 107, 83, 108, 111, 116, 46, 32, 84, 104, 101, 32, ...>>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the StateDb and BlockDb pruning paths referenced in the logs and reproduce the iterator errors during a long-running session. Identify why pruning fails for the affected tables, then verify that both pruning operations complete without errors and that database growth is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100