[
https://issues.apache.org/jira/browse/THRIFT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966132#comment-13966132
]
Marco Gallotta commented on THRIFT-1653:
----------------------------------------
I am also getting a continuously increasing number of connections left in a
CLOSE_WAIT state. It grows for a few hours until they consume all memory on a
server, and then processes are killed by the OOM killer. This is in using
Scribe, but I believe the problem lies within Thrift (potentially our
configuration of it). Using Thrift 0.9.1 with Scribe HEAD from Github.
> TThreadedSelectorServer leaks CLOSE_WAIT sockets
> -------------------------------------------------
>
> Key: THRIFT-1653
> URL: https://issues.apache.org/jira/browse/THRIFT-1653
> Project: Thrift
> Issue Type: Bug
> Reporter: Mikhail Bautin
> Assignee: Jake Farrell
> Fix For: 0.9
>
>
> We are using TThreadedSelectorServer in HBase regionserver. We are observing
> that under high load thousands of sockets in the CLOSE_WAIT state are not
> being cleaned up, leading to server crash. Is it possible that the sockets
> are not being closed on the server side, or the process of closing sockets
> closed by client is being starved on the server, because normal I/O takes
> priority?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
