Skip to content

Commit 0f11cf8

Browse files
committed
replace Jaysoni text
1 parent b7ff373 commit 0f11cf8

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

articles/application-gateway/features.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -102,11 +102,16 @@ For more information, see [WebSocket support](application-gateway-websocket.md)
102102

103103
## Connection draining
104104

105-
Connection draining helps you achieve graceful removal of backend pool members during planned service updates. This setting is enabled via the backend http setting and can be applied to all members of a backend pool during rule creation. Once enabled, Application Gateway ensures all deregistering instances of a backend pool don't receive any new request while allowing existing requests to complete within a configured time limit. This applies to both backend instances that are explicitly removed from the backend pool by a user configuration change, and backend instances that are reported as unhealthy as determined by the health probes. The only exception to this are requests bound for deregistering instances, which have been deregistered explicitly, because of gateway-managed session affinity and continues to be proxied to the deregistering instances.
105+
Connection draining helps you achieve graceful removal of backend pool members during planned service updates or problems with backend health. This setting is enabled via the [Backend Setting](configuration-http-settings.md) and is applied to all backend pool members during rule creation. Once enabled, the aplication gateway ensures all deregistering instances of a backend pool don't receive any new requests while allowing existing requests to complete within a configured time limit. It applies to cases where backend instances are:
106+
- explicitly removed from the backend pool after a configuration change by a user
107+
- reported as unhealthy by the health probes, or
108+
- removed during a scale-in operation
106109

107-
Connection draining is invoked for every single update to the gateway. To prevent connection loss to existing members of the backend pool, make sure to enable connection draining.
110+
The only exception is when requests continue to be proxied to the deregistering instances because of gateway-managed session affinity.
108111

109-
For more information, see [Application Gateway Configuration Overview](configuration-http-settings.md#connection-draining).
112+
The connection draining is honored for WebSocket connections as well. Connection draining is invoked for every single update to the gateway. To prevent connection loss to existing members of the backend pool, make sure to enable connection draining.
113+
114+
For information on time limits, see [Backend Settings configuration](configuration-http-settings.md#connection-draining).
110115

111116
## Custom error pages
112117

0 commit comments

Comments
 (0)