[
https://issues.apache.org/jira/browse/THRIFT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420927#comment-13420927
]
Mikhail Bautin commented on THRIFT-1653:
----------------------------------------
Dominik, Jake: thank you for your replies. We are using Linux with
/proc/sys/net/ipv4/tcp_fin_timeout value of 5 seconds. Is that low enough based
on your experience? If there is no bug in TThreadedSelectorServer (we could not
find anything obvious by reading the code), then another thing we could try is
to reconfigure the application to keep more connections open and create new
connections less frequently as a result.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
