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

Feature to use extra CL clients as fallbacks rather than simultaneously #2787

Closed
3 tasks
OisinKyne opened this issue Jan 12, 2024 · 2 comments
Closed
3 tasks
Labels

Comments

@OisinKyne
Copy link
Contributor

🎯 Problem to be solved

A user setup charon to point at two CLs in case the first one went down. Charon when given two CLs hits both and uses the fastest answer. This user would have been happier had there been a way to use the extra CLs as fallbacks only.

🛠️ Proposed solution

Create a --beacon-node-fallback-endpoints flag on charon run that takes a list of consensus clients, and use them only when the endpoints in the --beacon-node-endpoints are all unhealthy.

🧪 Tests

  • Tested by new automated unit/integration/smoke tests
  • Manually tested on core team/canary/test clusters
  • Manually tested on local compose simnet
@github-actions github-actions bot added the protocol Protocol Team tickets label Jan 12, 2024
@boulder225 boulder225 added the V1 label Mar 1, 2024
@pinebit
Copy link
Collaborator

pinebit commented Mar 14, 2024

Hey team! Please add your planning poker estimate with Zenhub @KaloyanTanev @gsora

@OisinKyne
Copy link
Contributor Author

Closing as duplicate of #3328

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants