-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
✨ add 10% jitter to ResyncPeriod #647
Conversation
Hi @xrmzju. Thanks for your PR. I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
@xrmzju: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @DirectXMan12 |
pkg/manager/manager.go
Outdated
SyncPeriod *time.Duration | ||
// value only if you know what you are doing. Defaults to 5 hours if unset. | ||
// the resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod | ||
MinResyncPeriod *time.Duration |
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.
This is a breaking change.
closing for now -- see my response on the associated issue |
I misunderstood the purpose earlier -- this is about adding jitter to the resync interval. We'll need to make that more clear (and not make this a breaking change) |
does [not make this a breaking change] means we should keep the |
Reusing the resync option and using it as input for the jitter seems reasonable to me, but if you have other thoughts let me know. More review inline |
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.
also, please include a full description of the change. Simply linking to the issue is insufficient.
Also, please delete the comments (the stuff between |
done |
/assign @DirectXMan12 |
/ok-to-test |
editted title to reflect current state /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DirectXMan12, xrmzju The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
all informers use the same resync period, this may cause multi controllers send list requests to apiserver simultaneously, add a jitter to resync period would be better.
fixes #648
this pr uses
ResyncPeriod
to add a jitter to theSyncPeriod
option before finally pass to theNewInformer
func