fix: skip the sync peer that does not belong to the scheduler cluster #3731
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.
Description
This pull request includes changes to the
manager/job/sync_peers.go
file to improve the synchronization of peers, specifically addressing compatibility with the Rust client. The most important changes include updating theSyncPeers
interface documentation and adding a condition to handle scheduler clusters in themergePeers
function.Documentation update:
manager/job/sync_peers.go
: Updated theSyncPeers
interface comment to specify that it is only supported in the Rust client.Functionality improvement:
manager/job/sync_peers.go
: Added a condition in themergePeers
function to skip sync peers that do not belong to the scheduler cluster, as the Golang client lacks theSchedulerClusterID
field.Related Issue
Motivation and Context
Screenshots (if appropriate)
Types of changes
Checklist