You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by db...@apache.org on 2022/01/25 23:13:35 UTC

[geode] branch revert-7294-feature/GEODE-9973-socket-lease-time-docs created (now a4c4f75)

This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a change to branch revert-7294-feature/GEODE-9973-socket-lease-time-docs
in repository https://gitbox.apache.org/repos/asf/geode.git.


      at a4c4f75  Revert "GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7294)"

This branch includes the following new commits:

     new a4c4f75  Revert "GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7294)"

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


[geode] 01/01: Revert "GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7294)"

Posted by db...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a commit to branch revert-7294-feature/GEODE-9973-socket-lease-time-docs
in repository https://gitbox.apache.org/repos/asf/geode.git

commit a4c4f75116f0b9cae9c4c14e0bcb6ce1d15f134e
Author: Dave Barnes <da...@vmware.com>
AuthorDate: Tue Jan 25 15:12:28 2022 -0800

    Revert "GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7294)"
    
    This reverts commit 763f590fe1e9a62ec21eae3a8c0cf0de2fee8594.
---
 .../monitor_tune/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 5caf93d..644c0f3 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 use the default value of `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 closes that socket. 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 returns it to the pool. 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`.
 
 ## <a id="socket_comm__section_936C6562C0034A2EAC9A63FFE9FDAC36" class="no-quick-link"></a>Calculating Connection Requirements