-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Remove Execution Client Fallback and Make Providing an Execution Client Required #10921
Conversation
@@ -105,46 +104,16 @@ func (s *Service) retryExecutionClientConnection(ctx context.Context, err error) | |||
// is ready to serve we connect to it again. This method is only | |||
// relevant if we are on our backup endpoint. | |||
func (s *Service) checkDefaultEndpoint(ctx context.Context) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We only have 1 endpoint now, this will basically cause prysm to keep on creating new connections to our execution node. This method should be removed since it serves no purpose with 0 fallback endpoints.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re-approving
Fixes #10588.
This PR removes all things related to execution client fallbacks, which will not be supported starting in v3. This also makes providing a non-empty execution client endpoint a requirement to run a node. Prysm nodes have a default value of localhost:8545 at this time