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.

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

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
Labels
protocol Protocol Team tickets

Comments

@boulder225
Copy link

🎯 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol Protocol Team tickets
Projects
None yet
Development

No branches or pull requests

3 participants
@gsora @boulder225 and others