[WIP] sync resource with the last resource version #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Iceber
force-pushed
the
last-resource-version
branch
2 times, most recently
from
4aa43c0
to
09ebc49
Compare
Iceber
force-pushed
the
last-resource-version
branch
from
09ebc49
to
f0fb6d1
Compare
Iceber
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When an exception happens in a cluster, in order to ensure that resource synchronization is not constantly retried,
we will stop retrying all resources of that cluster after two consecutive failed health checks.
The client-go
Reflectorwill have to list the full amount of data every time it starts up, and this can be a hug waste of resources when synchronizing multiple cluster resources.And since
clustersynchroalready knows the last synchronized resource version, we can use thelast sync resource versionto watch the cluster's resources, and then relist the full amount of resources when thelast sync resource versionexpired.This is also of great use when the
clustersynchro managerperforms master-slave switching.issue: #5