refactor: remove unused seed peer related logic #4259
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request removes the custom gRPC seed peer resolver implementation and its related usage from the codebase. The main impact is a simplification of the client connection logic for seed peers, as well as the cleanup of related interfaces and mock methods. The changes affect several packages, including the scheduler configuration and RPC client modules.
Removal of custom gRPC resolver and related logic
pkg/resolver/seed_peer_resolver.go
file, which previously implemented a custom gRPC resolver for seed peers. This includes the resolver registration, address resolution, and notification logic.GetResolveSeedPeerAddrs
method from theDynconfigInterface
inscheduler/config/dynconfig.go
, along with its implementation and associated imports. This method was used to provide dynamic addresses for the custom resolver. [1] [2] [3]GetClient
andGetV2
methods inpkg/rpc/cdnsystem/client/client.go
andpkg/rpc/dfdaemon/client/client_v2.go
, simplifying the client creation logic. [1] [2] [3]GetResolveSeedPeerAddrs
from the generated mock forDynconfigInterface
inscheduler/config/mocks/dynconfig_mock.go
. [1] [2]Miscellaneous cleanup
GetSeedPeerClusterConfigBySeedPeer
fromscheduler/config/dynconfig.go
, further simplifying the configuration code.Description
Related Issue
Motivation and Context
Screenshots (if appropriate)
Types of changes
Checklist