[
https://issues.apache.org/jira/browse/GEODE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124103#comment-15124103
]
ASF subversion and git services commented on GEODE-871:
-------------------------------------------------------
Commit 0994a45b5a584925b3c646b8b9607047c7869531 in incubator-geode's branch
refs/heads/feature/GEODE-831 from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0994a45 ]
Revert "GEODE-871: build-up of sockets in TIME_WAIT on locator machine"
This reverts commit c01506b27e233538ecc2ca5a81ca113c15cc388a.
> 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
> Assignee: Bruce Schuchardt
> Fix For: 1.0.0-incubating.M2
>
>
> 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)
