[
https://issues.apache.org/jira/browse/THRIFT-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290889#comment-16290889
]
James E. King, III commented on THRIFT-4230:
--------------------------------------------
Hi [~jegenberger], this doesn't ring a bell for me, however there still isn't
enough information in the bug report to go on. So far we know it was Thrift
0.9.3 and python, and I'm assuming that means python server. Which server was
being used? Nonblocking, Process pool, http? Which transport? Socket,
SSLSocket, twisted? Can it be boiled down to a simple example? It looks like
it could. Would THRIFT-3634 have addressed this?
> Thrift server connection may hang forever
> -----------------------------------------
>
> Key: THRIFT-4230
> URL: https://issues.apache.org/jira/browse/THRIFT-4230
> Project: Thrift
> Issue Type: Bug
> Components: Python - Library
> Affects Versions: 0.9.3
> Environment: OS: RHEL 7.2
> Reporter: Egor Kromberg
>
> After a lot of tests with HBASE Thrift server we found a problem.
> If the connection is dropped on the client side (using route or iptables) it
> may be still opened on the Thrift server side. Such situation will occur in
> case of unstable connection.
> After several iterations the Thrift server application will have a lot of
> opened connections and *will not accept *any new one. The only WA found is to
> restart the Thrift server.
> I believe Thrift server should have something like socket timeouts and
> heartbeats.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
