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

Charon cannot start if any beacon node is down #1312

Closed
corverroos opened this issue Oct 19, 2022 · 2 comments
Closed

Charon cannot start if any beacon node is down #1312

corverroos opened this issue Oct 19, 2022 · 2 comments
Assignees
@corverroos
Labels
bug Something isn't working

Comments

@corverroos
Copy link
Contributor

🐞 Bug Report

Problem to solve

Charon cannot start if any of the configured beacon-node-endpoints are not responding. So even though some beacon nodes are up and available, charon cannot start if only a single of the BNs are down.

This is due to go-eth2-client that fails to initialise if the BN is not accessible.

Proposed Solution

Wrap go-eth2-client instances in a LazyClient type that tries to initialise the underlying client on each API call if not initialised yet.
@OisinKyne OisinKyne added the bug Something isn't working label Jan 11, 2023
@OisinKyne
Copy link
Contributor

Is this long fixed? @corverroos

@corverroos
Copy link
Contributor Author

this isn't fixed no

@xenowits xenowits assigned corverroos and unassigned xenowits Feb 2, 2023
@corverroos corverroos mentioned this issue Feb 2, 2023
Merged
obol-bulldozer bot pushed a commit that referenced this issue Feb 3, 2023
@corverroos
app/eth2wrap: add lazy init (#1760)
0be141a 
Wraps eth2clients in a "lazy loader", this allows charon to start even if one or more beacon nodes are down (as long as one is up and available).

category: feature
ticket: #1312
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@corverroos corverroos

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@OisinKyne @corverroos @xenowits