-
Notifications
You must be signed in to change notification settings - Fork 551
Attempt to start list watch from last resourceVersion #711
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
Attempt to start list watch from last resourceVersion #711
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. I understand the commands that are listed here. |
Welcome @bbatha! |
This change should avoid unnecessary calls to the listFn that populates the ListWatch cache by first attempting to start the watch from the last resourceVersion. If a 410 Gone is detected it will fallback to the full list call.
ec23213
to
e7f758e
Compare
I signed it |
/check-cla |
src/cache.ts
Outdated
@@ -120,7 +120,9 @@ export class ListWatch<T extends KubernetesObject> implements ObjectCache<T>, In | |||
|
|||
private async doneHandler(err: any): Promise<any> { | |||
this._stop(); | |||
if (err) { | |||
if (err?.message === 'Gone') { |
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.
Please check the status code (410) vs the text
src/cache.ts
Outdated
} | ||
}); | ||
this.addOrUpdateItems(list.items); | ||
queryParams.resourceVersion = list.metadata!.resourceVersion; |
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.
Shouldn't this be this.resourceVersion
?
Requested changes made. |
@@ -197,7 +197,9 @@ describe('ListWatchCache', () => { | |||
} as V1ObjectMeta, | |||
} as V1Namespace); | |||
|
|||
await doneHandler(null); | |||
const error = new Error('Gone') as Error & { statusCode: number | undefined }; |
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.
These two tests relied on doneHandler
calling listFn
every time.
This looks good to me, but something is still messed up w/ your CLA. |
/check-cla |
@brendanburns CLA issues sorted out, thanks for the quick reviews! |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bbatha, brendandburns 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 |
This change should avoid unnecessary calls to the listFn that populates
the ListWatch cache by first attempting to start the watch from the last
resourceVersion. If a 410 Gone is detected it will fallback to the full
list call.