Skip to content
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

High Latency from AKS to Azure Storage #1587

Closed
dewanymca opened this issue May 2, 2020 · 9 comments
Closed

High Latency from AKS to Azure Storage #1587

dewanymca opened this issue May 2, 2020 · 9 comments
Labels
resolution/answer-provided Provided answer to issue, question or feedback.

Comments

@dewanymca
Copy link

dewanymca commented May 2, 2020

HI Team

We have been using AKS workload to connect to Azure storage, we are experiencing latency in call to Azure Storage, It goes into 5-7 seconds, we checked with storage team and they confirmed there is no latency on storage side and calls are getting completed in msec.

Also, we are running same code from Azure App service and there we are not experiencing any latency to same storage. can you please help us in identifying from where this latency is coming.

Attaching latency graph from storage:
image

Thanks
Deepak

@andyzhangx
Copy link
Contributor

@dewanymca how did you use azure storage? pod talk to azure storage directly? is it related to DNS resolution?

@dewanymca
Copy link
Author

Pod directly talks to storage using storage sdk with Auth token which is being provided by pod identity. We are not sure whether DNs resolution is the issue or not. One thing we can say for sure we have tested same application in aks in non production environment under load but never ran into this high latency.

@GuyPaddock
Copy link

This sounds similar to what we are seeing in #1593. In that case, just unzipping a large ZIP file on a share with no other traffic leads to latency that's so bad that the Azure Files mount becomes unresponsive.

@dewanymca
Copy link
Author

@GuyPaddock thanks for pointer, however we are not using volume, app is making a connection to storage directly via SDK so i think #1593 is not applicable in this case.

@andyzhangx
Copy link
Contributor

it's caused by DNS resolution latency as discussed offline.

@github-actions
Copy link

Action required from @Azure/aks-pm

@ghost
Copy link

ghost commented Jul 26, 2020

Action required from @Azure/aks-pm

@ghost ghost added the Needs Attention 👋 Issues needs attention/assignee/owner label Jul 26, 2020
@palma21 palma21 added resolution/answer-provided Provided answer to issue, question or feedback. and removed Needs Attention 👋 Issues needs attention/assignee/owner action-required labels Jul 27, 2020
@palma21
Copy link
Member

palma21 commented Jul 27, 2020

Marking with answer provided. Please reach out if not the case.

@ghost
Copy link

ghost commented Jul 29, 2020

Thanks for reaching out. I'm closing this issue as it was marked with "Answer Provided" and it hasn't had activity for 2 days.

@ghost ghost closed this as completed Jul 29, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Aug 28, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolution/answer-provided Provided answer to issue, question or feedback.
Projects
None yet
Development

No branches or pull requests

4 participants