lambdaclass / lambdaclass/lambda_ethereum_consensus
Investigate Genserver restart conditions
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We have genservers in a supervisor tree but when they are restarted due to a failure, the new state is not in sync with the rest of the app.
One example of this is this bug: https://github.com/lambdaclass/lambda_ethereum_consensus/issues/851
As part of this ticket we should look into the genservers and verify that restarting them keeps the app working properly.
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 reading the linked bug in issue #851 and then inventory the genservers and supervisor trees involved in the reported restart path. Compare state before and after a failure and define which shared state must remain synchronized; the work is done when restart behavior is verified across the affected genservers and the application continues working correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100