[
https://issues.apache.org/jira/browse/GEODE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121841#comment-15121841
]
ASF subversion and git services commented on GEODE-871:
-------------------------------------------------------
Commit c01506b27e233538ecc2ca5a81ca113c15cc388a in incubator-geode's branch
refs/heads/develop from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=c01506b ]
GEODE-871: build-up of sockets in TIME_WAIT on locator machine
This change-set alters the client to abort its TCP/IP connection to
the locator by enabling SO_LINGER and setting the timeout to zero
before it closes the connection. The Locator closes its connection
first, which puts it into TIME_WAIT. The client then aborts the
connection, which cleans up the Locator's TIME_WAIT connection.
> Frequent use of executeOnAllServers causes build-up of sockets in TIME_WAIT
> on locator machine
> ----------------------------------------------------------------------------------------------
>
> Key: GEODE-871
> URL: https://issues.apache.org/jira/browse/GEODE-871
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Reporter: Bruce Schuchardt
>
> The executeOnAllServers implementation contacts a locator in order to get the
> current set of servers. This opens a TCP/IP connection to the locator,
> interacts with the locator and then closes the TCP/IP connection. The
> connection is ending up in TIME_WAIT state though, indicating that the
> locator is usually initiating the close of the connection instead of the
> client.
> These TIME_WAIT TCP/IP connections can build up rapidly and cause the locator
> to run out of ephemeral ports. That puts the locator out of commission until
> the connections are timed out by the OS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
