[
https://issues.apache.org/jira/browse/THRIFT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652984#comment-13652984
]
Dian FAN commented on THRIFT-1653:
----------------------------------
my understanding is that close_wait is different from time_wait.
most likely it should be a bug that the Thrift server side does not properly
send FIN to the already-closed client side.
I guess some fine tuning of TCP keepalive parameters could reduce the count of
dead connections at the server side, but that does not fix the application
layer bug.
should we reopen it?
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
