fix: optimize reconciliation for large clusters #1
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
Optimize Redis Operator for managing large numbers of objects (hundreds/thousands of Redis resources).
Problems solved:
Reconciled()was used instead ofRequeueAfter()when StatefulSet is not readyChanges:
Owns(&appsv1.StatefulSet{})to Redis and RedisReplication controllers for event-driven reconciliation instead of pollingReconciled()was used instead ofRequeueAfterwhen StatefulSet is not ready, causing objects to get stuckExpected impact:
Type of change
Checklist