I need to set is "idle timeout", but our "Azure Application Gateway" does not have this parameter.

Question

I need to set is "idle timeout", but our "Azure Application Gateway" does not have this parameter.

José Antonio Trejo Gutiérrez 45

Good day,

We have an ARO-Openshift cluster where we have installed several applications and we use an "Azure Application Gateway" to consume these applications on our own network. In this cluster we have streams to several databases and with the applications we execute queries to these databases and it works fine, however we have a problem with long running queries, we get:

<center><h1>502 Bad Gateway</h1></center>

<hr><center>Microsoft-Azure-Application-Gateway/v2</center>

Reading on the internet (https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-tcp-idle-timeout?tabs=tcp-reset-idle-cli), we find that the timeout we need to set is "idle timeout", but our "Azure Application Gateway" does not have this parameter and we have no idea how to fix it, so we ask your valuable help. to fix it as the mexico azure team has been unable to help with this issue.

The specifications of our infrastructure are:

Openshift : 4.10.20

AAGW: V2 standard

Best regards.

GitaraniSharma-MSFT 49,881 Reputation points Microsoft Employee

2023-05-29T08:49:42.6133333+00:00

Hello @José Antonio Trejo Gutiérrez , Just checking in to see if you had a chance to see the below answer. To help the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer.

And, if you have any further questions do let us know.
José Antonio Trejo Gutiérrez 45 Reputation points

2023-05-30T01:50:08.24+00:00

Thank you very much @GitaraniSharma-MSFT , I tried what you say but unfortunately the problem persists.
GitaraniSharma-MSFT 49,881 Reputation points Microsoft Employee

2023-05-30T10:51:48.5933333+00:00

Hello @José Antonio Trejo Gutiérrez , thank you for the update. I've emailed you regarding the further steps. Could you please check the same and reply with the details requested? Thank you!
José Antonio Trejo Gutiérrez 45 Reputation points

2023-05-31T16:05:46.35+00:00

Thank you very much @GitaraniSharma-MSFT , we really appreciate your help, what you showed me gave me the clue I needed to find the actual timeout I needed to set, it was not on the public IP, it was on the virtual network/subnet and it was the flow timeout, I set it to 30 minutes and now the message appears at minute 30 and not at minute 4, that allows me to solve 90% of my queries, however if I could increase this limit that would be great.
KapilAnanth-MSFT 49,276 Reputation points Microsoft Employee

2023-06-01T04:35:53.38+00:00

@José Antonio Trejo Gutiérrez

Greetings.

Currently, Azure Virtual Networks support FlowTimeout between 4 and 30 minutes (inclusive)

If your focus is to make the application gateway wait for a more period of time for a response from a backend pool, you can try changing the Request time out in BackendSettings .

This should support upto 24 hours for a Private backend.

Refer : App Gateway Limits

Cheers,

Kapil
Ricardo Gabriel Nima Montalban 0 Reputation points

2023-08-08T23:09:41.29+00:00

Hello @GitaraniSharma-MSFT I have two similar scenarios but with public IP for azure application gateway Standar V2. One using AKS as backend pool and other using VMs as backend pool, in both cases I have 502 errors using jmeter tool. I usually got 0.03% of 502 errors in tests. I have tried adding more instances for appGW, adding more pods for my application, wich is based on spring boot, but the 502 errors persist. But if I use Nginx servers plus a load balancer as front I got 0 errors with the same VMs backend pool. What do you consider I must check, coul you help me please.

Accepted answer

0 additional answers

Your answer

GitaraniSharma-MSFT 49,881 Reputation points Microsoft Employee

2023-05-29T08:49:42.6133333+00:00

Hello @José Antonio Trejo Gutiérrez , Just checking in to see if you had a chance to see the below answer. To help the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer.

And, if you have any further questions do let us know.
José Antonio Trejo Gutiérrez 45 Reputation points

2023-05-30T01:50:08.24+00:00

Thank you very much @GitaraniSharma-MSFT , I tried what you say but unfortunately the problem persists.
GitaraniSharma-MSFT 49,881 Reputation points Microsoft Employee

2023-05-30T10:51:48.5933333+00:00

Hello @José Antonio Trejo Gutiérrez , thank you for the update. I've emailed you regarding the further steps. Could you please check the same and reply with the details requested? Thank you!
José Antonio Trejo Gutiérrez 45 Reputation points

2023-05-31T16:05:46.35+00:00

Thank you very much @GitaraniSharma-MSFT , we really appreciate your help, what you showed me gave me the clue I needed to find the actual timeout I needed to set, it was not on the public IP, it was on the virtual network/subnet and it was the flow timeout, I set it to 30 minutes and now the message appears at minute 30 and not at minute 4, that allows me to solve 90% of my queries, however if I could increase this limit that would be great.
KapilAnanth-MSFT 49,276 Reputation points Microsoft Employee

2023-06-01T04:35:53.38+00:00

@José Antonio Trejo Gutiérrez

Greetings.

Currently, Azure Virtual Networks support FlowTimeout between 4 and 30 minutes (inclusive)

If your focus is to make the application gateway wait for a more period of time for a response from a backend pool, you can try changing the Request time out in BackendSettings .

This should support upto 24 hours for a Private backend.

Refer : App Gateway Limits

Cheers,

Kapil
Ricardo Gabriel Nima Montalban 0 Reputation points

2023-08-08T23:09:41.29+00:00

Hello @GitaraniSharma-MSFT I have two similar scenarios but with public IP for azure application gateway Standar V2. One using AKS as backend pool and other using VMs as backend pool, in both cases I have 502 errors using jmeter tool. I usually got 0.03% of 502 errors in tests. I have tried adding more instances for appGW, adding more pods for my application, wich is based on spring boot, but the 502 errors persist. But if I use Nginx servers plus a load balancer as front I got 0 errors with the same VMs backend pool. What do you consider I must check, coul you help me please.

Answer 1

Hello @José Antonio Trejo Gutiérrez ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you would like to where to set "idle timeout" setting on your Azure Application Gateway.

As mentioned in our Azure Application gateway FAQ document,

What are the settings for Keep-Alive timeout and TCP idle timeout?

Keep-Alive timeout governs how long the Application Gateway waits for a client to send another HTTP request on a persistent connection before reusing it or closing it.
TCP idle timeout governs how long a TCP connection is kept open if there's no activity.

The Keep-Alive timeout in the Application Gateway v1 SKU is 120 seconds and in the v2 SKU it's 75 seconds.

The TCP idle timeout is a 4-minute default on the frontend virtual IP (VIP) of both v1 and v2 SKU of Application Gateway. You can configure the TCP idle timeout value on v1 and v2 Application Gateways to be anywhere between 4 minutes and 30 minutes.

For both v1 and v2 Application Gateways, you need to navigate to the public IP of the Application Gateway and change the TCP idle timeout under the "Configuration" blade of the public IP on Portal. Changing the value of the private IP address isn't supported.

You can set the TCP idle timeout value of the public IP through PowerShell by running the following commands:

$publicIP = Get-AzPublicIpAddress -Name MyPublicIP -ResourceGroupName MyResourceGroup
$publicIP.IdleTimeoutInMinutes = "15"
Set-AzPublicIpAddress -PublicIpAddress $publicIP

NOTE: For HTTP/2 connections to the frontend IP address on Application Gateway v2 SKU, the idle timeout is set to 180 seconds and is non-configurable.

To configure this setting via Azure Portal, follow the below steps:

Go to your Application gateway in Azure Portal and click on the Frontend public IP address listed on it's Overview page:

enter image description here

On the Public IP address page, go to Configuration pane:

enter image description here

Drag the Idle timeout bar to your required number:

NOTE: You can configure the TCP idle timeout value on v1 and v2 Application Gateways to be anywhere between 4 minutes and 30 minutes.

enter image description here

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Chase, Justin M 0 Reputation points

2024-02-07T20:20:36.73+00:00

How can we configure it to be different based on the Content-Type of the response?

For example, this web standard:
https://medium.com/@kova98/server-sent-events-in-net-7f700b21cdb7

When a user calls an event stream controller, the standard is to respond with headers right away but then the body will stream out based on the events. You can have long periods of inactivity between events.

How can we increase the timeout for text/event-stream responses specifically?
GitaraniSharma-MSFT 49,881 Reputation points Microsoft Employee

2024-03-07T11:36:03.8766667+00:00

Hello @Chase, Justin M ,

Apologies for the delay in response as I missed this comment.

The only timeout settings that Azure Application gateway allows you to configure is either in its backend settings (number of seconds that the application gateway waits to receive a response from the backend server) or the TCP idle timeout setting (how long a TCP connection is kept open if there's no activity) in its Public IP. There is no way to configure it to be different based on the Content-Type of the response.

Refer: https://learn.microsoft.com/en-us/azure/application-gateway/configuration-http-settings#request-timeout

https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-faq#what-are-the-settings-for-keep-alive-timeout-and-tcp-idle-timeout

https://learn.microsoft.com/en-us/azure/application-gateway/http-response-codes#504--gateway-timeout

https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-troubleshooting-502#request-time-out

If you wish you may also leave your feedback in the below forum requesting this feature. All the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.

https://feedback.azure.com/d365community/forum/8ae9bf04-8326-ec11-b6e6-000d3a4f0789

Regards,

Gita

Share via

I need to set is "idle timeout", but our "Azure Application Gateway" does not have this parameter.

0 additional answers

Your answer