Skip to content

Commit fac03b2

Browse files
authored
Merge pull request #206984 from flang-msft/fxl-github-issue-Some-Linux-versions-use-optimistic-TCP-settings-by-default.-
fxl---rewording for localization
2 parents dffaf0a + d050859 commit fac03b2

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/azure-cache-for-redis/cache-best-practices-connection.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,10 @@ title: Best practices for connection resilience
33
titleSuffix: Azure Cache for Redis
44
description: Learn how to make your Azure Cache for Redis connections resilient.
55
author: flang-msft
6+
67
ms.service: cache
78
ms.topic: conceptual
8-
ms.date: 11/3/2021
9+
ms.date: 08/03/2022
910
ms.author: franlanglois
1011
---
1112

@@ -21,7 +22,9 @@ Test your system's resiliency to connection breaks using a [reboot](cache-admini
2122

2223
## TCP settings for Linux-hosted client applications
2324

24-
Some Linux versions use optimistic TCP settings by default. The TCP settings can create a situation where a client connection to a cache cannot be reestablished for a long time when a Redis server stops responding before closing the connection gracefully. The failure to reestablish a connection can happen if the primary node of your Azure Cache For Redis becomes unavailable, for example, for unplanned maintenance.
25+
Some Linux versions use TCP settings that are too high by default. The higher TCP settings can create a situation where a client connection to a cache cannot be reestablished for a long time when a Redis server stops responding. The client waits too long before closing the connection gracefully.
26+
27+
The failure to reestablish a connection can happen if the primary node of your Azure Cache For Redis becomes unavailable, for example, for unplanned maintenance.
2528

2629
We recommend these TCP settings:
2730

0 commit comments

Comments
 (0)