-
Notifications
You must be signed in to change notification settings - Fork 200
fix: adjust the batch size as per the number of disks allowed #3039
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
fix: adjust the batch size as per the number of disks allowed #3039
Conversation
Skipping CI for Draft Pull Request. |
/test all |
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.
thanks for the PR, I have left some comments.
btw, the original Elastic issue is mainly contributed by retry-after value returned by CRP during polling, this On the other hand, I think this PR is still valuable which could make most disk attach succeed in the beginning. Thanks for the fix. |
8b880e3
to
186c5c0
Compare
186c5c0
to
6a08037
Compare
This reverts commit 996d296.
/retest |
1 similar comment
/retest |
@@ -444,16 +445,16 @@ func (d *Driver) NodeGetInfo(ctx context.Context, _ *csi.NodeGetInfoRequest) (*c | |||
}, nil | |||
} | |||
|
|||
func getMaxDataDiskCount(instanceType string) int64 { | |||
func getMaxDataDiskCount(instanceType string) (int64, bool) { |
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.
can you add ut for returned bool value check in another PR? thx
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx, nearora-msft 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 |
/cherrypick release-1.32 |
/cherrypick release-1.31 |
@andyzhangx: #3039 failed to apply on top of branch "release-1.31":
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. |
@andyzhangx: new pull request created: #3073 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. |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Requirements:
Special notes for your reviewer:
Release note: