From f574632746e44dc283b91c98b867c82487172a19 Mon Sep 17 00:00:00 2001 From: Donal Evans Date: Wed, 26 Jan 2022 14:17:23 -0800 Subject: [PATCH] GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310) --- .../socket_communication_have_enough_sockets.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb index 1c52ed5dbf95..f2ec5e8351cf 100644 --- a/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb +++ b/geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb @@ -39,7 +39,7 @@ recommend that you set `conserve-sockets` to `false`. You can force the release of an idle socket connection for peer-to-peer and client-to-server connections: -- **Peer-to-peer**. For peer-to-peer threads that do not share sockets, you can use the `socket-lease-time` to make sure that no socket sits idle for too long. When a socket that belongs to an individual thread remains unused for this time period, the system automatically returns it to the pool. The next time the thread needs a socket, it creates a new socket. +- **Peer-to-peer**. For peer-to-peer threads that do not share sockets, you can use the `socket-lease-time` to make sure that no socket sits idle for too long. When a socket that belongs to an individual thread remains unused for this time period, the system automatically closes that socket. The next time the thread needs a socket, it creates a new socket. - **Client**. For client connections, you can affect the same lease-time behavior by setting the pool `idle-timeout`. ## Calculating Connection Requirements