[ https://issues.apache.org/jira/browse/THRIFT-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289813#comment-16289813 ]
Jeremy Egenberger edited comment on THRIFT-4230 at 12/13/17 8:18 PM: --------------------------------------------------------------------- Does anybody know if this is fixed in a subsequent version of Thrift? I don't see anything in the release notes but could it have been fixed inadvertently? Priority is "Major" and it does sound like a major issue, but this record hasn't been updated in a while and I'm having trouble finding other references to it. was (Author: jegenberger): Does anybody know if this is fixed in a subsequent version of Thrift? I don't see anything in the release notes but could it have been fixed inadvertently? Priority is "Major" and it does sound like major issue, but this record hasn't been updated in a while and I'm having trouble finding other references to it. > Thrift server connection may hang forever > ----------------------------------------- > > Key: THRIFT-4230 > URL: https://issues.apache.org/jira/browse/THRIFT-4230 > Project: Thrift > Issue Type: Bug > Components: Java - Library > 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)