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

Implement Fallback Beacon Node Selection for Charon #3328

Open
8 tasks
boulder225 opened this issue Oct 9, 2024 · 0 comments
Open
8 tasks

Implement Fallback Beacon Node Selection for Charon #3328

boulder225 opened this issue Oct 9, 2024 · 0 comments
Assignees
@gsora
Labels
protocol Protocol Team tickets
Milestone
v1.3.0

Comments

@boulder225
Copy link

boulder225 commented Oct 9, 2024 •
edited by KaloyanTanev
Loading

🎯 Problem to be solved

Charon currently doesn't have a reliable way to handle beacon node failures, which could lead to interruptions. We need to improve Charon's ability to switch to backup beacon nodes when the primary node fails.

🛠️ Proposed solution

  • Implement a "pick list" feature in Charon for fallback beacon nodes
  • Allow users to specify a list of primary and fallback beacon nodes through configuration
  • When a call to a primary beacon node fails, automatically try the next available node from the fallback list
  • If all nodes in the list fail, report the failure to Charon
  • Ensure this feature works with the existing "multi" component that handles multiple beacon node connections
  • Add error handling and logging for fallback node selection
  • Update documentation to explain how to use and configure the fallback beacon node feature
  • Create tests to verify the fallback mechanism works as expected
@github-actions github-actions bot added the protocol Protocol Team tickets label Oct 9, 2024
@gsora gsora mentioned this issue Oct 15, 2024
Merged
@OisinKyne OisinKyne added this to the v1.3.0 milestone Dec 12, 2024
@OisinKyne OisinKyne mentioned this issue Dec 12, 2024
Closed
3 tasks
obol-bulldozer bot pushed a commit that referenced this issue Jan 7, 2025
@gsora
app/eth2wrap: fallback beacon nodes (#3342)
6a0caf4 
Implement a way to provide eth2wrap with two classes of beacon nodes addresses: standard and fallback beacon nodes.

When one of the multi BN calls fails, eth2wrap wrappers will try to get an available fallback BN from a list and re-do the call on that.

If no fallback BNs is specified, return the original error.

If the fallback BN call fails, return fallback error instead.

This PR firstly introduces concepts and code, will introduce CLI parameters and initialization code later.

category: feature
ticket: #3328
DiogoSantoss pushed a commit that referenced this issue Jan 7, 2025
@gsora @DiogoSantoss
app/eth2wrap: fallback beacon nodes (#3342)
6ca5bf7 
Implement a way to provide eth2wrap with two classes of beacon nodes addresses: standard and fallback beacon nodes.

When one of the multi BN calls fails, eth2wrap wrappers will try to get an available fallback BN from a list and re-do the call on that.

If no fallback BNs is specified, return the original error.

If the fallback BN call fails, return fallback error instead.

This PR firstly introduces concepts and code, will introduce CLI parameters and initialization code later.

category: feature
ticket: #3328
DiogoSantoss pushed a commit that referenced this issue Jan 14, 2025
@gsora @DiogoSantoss
app/eth2wrap: fallback beacon nodes (#3342)
caec6c3 
Implement a way to provide eth2wrap with two classes of beacon nodes addresses: standard and fallback beacon nodes.

When one of the multi BN calls fails, eth2wrap wrappers will try to get an available fallback BN from a list and re-do the call on that.

If no fallback BNs is specified, return the original error.

If the fallback BN call fails, return fallback error instead.

This PR firstly introduces concepts and code, will introduce CLI parameters and initialization code later.

category: feature
ticket: #3328
@DiogoSantoss DiogoSantoss mentioned this issue Jan 14, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gsora gsora

Labels
protocol Protocol Team tickets
Projects
None yet
Milestone
v1.3.0
Development

No branches or pull requests
4 participants
@gsora @OisinKyne @boulder225 and others