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?
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)?
dhruvinparikh
commented
2 weeks ago
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?
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