Skip to content

Commit 6c20424

Browse files
Merge pull request #213384 from vhorne/fw-long-running
change to scale in
2 parents 0713659 + 71eddda commit 6c20424

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/firewall/long-running-sessions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: firewall
55
author: vhorne
66
ms.service: firewall
77
ms.topic: article
8-
ms.date: 09/22/2022
8+
ms.date: 10/03/2022
99
ms.author: victorh
1010
---
1111

@@ -16,14 +16,14 @@ Azure Firewall is designed to be available and redundant. Every effort is made t
1616
## Scenarios that impact long running TCP sessions
1717

1818
The following scenarios can potentially drop long running TCP sessions:
19-
- Scale down
19+
- Scale in
2020
- Firewall maintenance
2121
- Idle timeout
2222
- Auto-recovery
2323

24-
### Scale down
24+
### Scale in
2525

26-
Azure Firewall scales up\down based on throughput and CPU usage. Scale down is performed by putting the VM instance in drain mode for 90 seconds before recycling the VM instance. Any long running connections remaining on the VM instance after 90 seconds will be disconnected.
26+
Azure Firewall scales in/out based on throughput and CPU usage. Scale in is performed by putting the VM instance in drain mode for 90 seconds before recycling the VM instance. Any long running connections remaining on the VM instance after 90 seconds will be disconnected.
2727

2828
### Firewall maintenance
2929

0 commit comments

Comments
 (0)