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

Validator Client gRPC Load Balancing #14133

Open
LZF-2019 opened this issue Jun 24, 2024 · 0 comments · May be fixed by #14144
Open

Validator Client gRPC Load Balancing #14133

LZF-2019 opened this issue Jun 24, 2024 · 0 comments · May be fixed by #14144
Assignees
Labels
Bug Something isn't working

Comments

@LZF-2019
Copy link

Describe the bug

Hi,all
My validator is using the --beacon-rpc-provider option to set two different beacon addresses for failover purposes. I understand the current strategy is to connect to the first beacon address and perform the work, and switch to the second beacon address only when the first one becomes unreachable, which works as expected in practice. However, I noticed that the switching interval is a bit too long, taking around 10 minutes (or even longer in some cases). For the work of the validator, I feel this failover time might be too long to accept.

My question is, what considerations were taken into account for this failover switching strategy, and is there a way to trigger the switching more quickly?
image
image

Has this worked before in a previous version?

No response

🔬 Minimal Reproduction

No response

Error

No response

Platform(s)

Linux (x86)

What version of Prysm are you running? (Which release)

5.0.3

Anything else relevant (validator index / public key)?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
2 participants