-
Notifications
You must be signed in to change notification settings - Fork 849
Cache known bad ids to remove from batch calls #2817
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
base: master
Are you sure you want to change the base?
Conversation
Code Coverage Diff
|
c9fb524 to
c157257
Compare
|
/retest |
1 similar comment
|
/retest |
ConnorJC3
left a comment
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.
/lgtm
|
/lgtm Waiting on manual testing instructions for approval |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/hold |
|
/unhold |
torredil
left a comment
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 revision looks great. The logic is sound, edge cases are handled correctly, and code coverage is comprehensive. If we could run this through a scale test before release that would be sweet.
/lgtm
Running one as we speak :) |
What type of PR is this?
/kind feature
What is this PR about? / Why do we need it?
This PR improves our batching process by adding a cache to put known bad IDs into for Volumes,snapshots and instances. When a request comes in with a known bad id we trim it from the batch request and try it separately from the batch. This ensures one bad ID does not constantly poison the whole batch.
How was this change tested?
Volume Example
Statically provisioned a fake volume
Modified the volume
Without Change
With change
Snapshots example
Create a Snapshot with a fake snapshot id
Instance Example
Crate a fake CSI-node object a fake Node object and a fake volume-Attachemnt
example yaml
Does this PR introduce a user-facing change?
working on unit tests and finishing up manual testing WIP