-
Notifications
You must be signed in to change notification settings - Fork 40.7k
Clean backoff record earlier #132109
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
Clean backoff record earlier #132109
Conversation
please add release note, certainly this PR results in user-facing change. |
@linxiulei I left some comments. Overall I think this approach could work, but I have some hesitations about corner cases races. I'm wondering if another approach is simpler, like clearing the backoffStore in case the Job is newly created, based on empty Status, for example detected by checking that status.startTime=nil (this way we can tell this is the first reconcile). wdyt? |
Once received job deletion event, it cleans the backoff records for that job before enqueueing this job so that we can avoid a race condition that the syncJob() may incorrect use stale backoff records for a newly created job with same key. Co-authored-by: Michal Wozniak <michalwozniak@google.com>
/triage accepted leaving the final tag on @mimowo |
@atiratree: The label(s) 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: atiratree, linxiulei 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 |
/priority important-soon |
/lgtm Leaving approve to @atiratree I'm supportive to cherry-pick, because:
|
LGTM label has been added. Git tree hash: be1742a7c6964d7974931b018c879997e30d92f6
|
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #132042
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: