-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Set custom PollingDelay of 5 seconds for Azure VirtualMachinesClient #40066
Set custom PollingDelay of 5 seconds for Azure VirtualMachinesClient #40066
Conversation
The default polling delay of 1 minute results in very long delays when an Azure Disk is attached to a node. It gets worse as go-autorest doubles the default delay to 2 minutes. Please see: kubernetes#35180 (comment) Only the PollingDelay for VirtualMachinesClient is modified here to avoid too much pressure on Azure quotas.
Hi @codablock. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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. |
I was asked to add some more information about timing data. Without this change, it takes at least 2 minutes for attachment and also for detachment. This means, if a volume needs to be reattached to another node, it takes at least 4 minutes to complete. With this PR applied, this is reduced to something like 40 seconds per operation, which is not optimal but still a lot better. These timing are only for the attach/detach part of the Azure volumes. It does not take into account the time needed to format and mount the volumes. There are other issues and PRs working on these. |
LGTM. Burns some quota, but only when attaching/detaching and the speedup seems worth it. |
@k8s-bot ok to test /lgtm |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Thanks for the LGTM :) I think this is a good and safe candidate for a 1.5.x cherry-pick. I'm still not sure how this is initiated. Is it enough to ping the saad-ali? |
ping @saad-ali for a 1.5.x cherry-pick. |
Commit found in the "release-1.5" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
The default polling delay of 1 minute results in very long delays when
an Azure Disk is attached to a node. It gets worse as go-autorest
doubles the default delay to 2 minutes.
Please see: #35180 (comment)
Only the PollingDelay for VirtualMachinesClient is modified here to
avoid too much pressure on Azure quotas.
Release Nodes: