-
Notifications
You must be signed in to change notification settings - Fork 2k
Fixes watch conflict handling in informer and more test coverage #522
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
Fixes watch conflict handling in informer and more test coverage #522
Conversation
0a4b690
to
afa4671
Compare
afa4671
to
0ec1855
Compare
@@ -99,7 +99,7 @@ public void run() { | |||
return; | |||
} | |||
log.error("{}#Watch failed as {} unexpected", apiTypeClass, t.getMessage(), t); | |||
continue; | |||
return; |
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.
the first bug uncovered by conflicting watch event
when a event arrives w/ ERROR type, the reflector should started another round of listing but it's now keeping retrying watch. the bug happens when the event is resourceVersion
confliction error, the watch will always be failing b/c it requests w/ an outdated resourceVersion
. should return in this case, so that it can fetches the latest resourceVersion by re-listing
/cc @brendandburns
0ec1855
to
c838490
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, yue9944882 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 |
No description provided.