You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/03/18 16:54:00 UTC

[jira] [Commented] (GEODE-9973) Documentation: socket-lease-time is not used to return sockets to a pool but to close them

    [ https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508924#comment-17508924 ] 

ASF subversion and git services commented on GEODE-9973:
--------------------------------------------------------

Commit 0162fed255cc7708ea6e476ff3e0f9300660d4f4 in geode's branch refs/heads/master from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0162fed ]

GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7310)



> Documentation: socket-lease-time is not used to return sockets to a pool but to close them
> ------------------------------------------------------------------------------------------
>
>                 Key: GEODE-9973
>                 URL: https://issues.apache.org/jira/browse/GEODE-9973
>             Project: Geode
>          Issue Type: Bug
>          Components: docs
>    Affects Versions: 1.12.9, 1.13.8, 1.14.4, 1.15.0
>            Reporter: Alberto Gomez
>            Assignee: Donal Evans
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0
>
>
> The "Making sure you have enough sockets" Geode documentation section says the following about socket-lease-time (check underlined sentence):
>  
> 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.
>  
> Actually, the system automatically closes the connection in the situation described instead of returning it to any pool.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)