Mailing-List: contact dev-help@thrift.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@thrift.apache.org
Date: Mon, 18 Dec 2017 18:57:00 +0000 (UTC)
From: "Jeremy Egenberger (JIRA)" <jira@apache.org>
To: dev@thrift.apache.org
Message-ID: <JIRA.13080336.1497596705000.484899.1513623420584@Atlassian.JIRA>
In-Reply-To: <JIRA.13080336.1497596705000@Atlassian.JIRA>
References: <JIRA.13080336.1497596705000@Atlassian.JIRA> <JIRA.13080336.1497596705865@jira-lw-us.apache.org>
Subject: [jira] [Commented] (THRIFT-4230) Thrift server connection may hang
 forever
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 18 Dec 2017 18:57:06 -0000


    [ https://issues.apache.org/jira/browse/THRIFT-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295464#comment-16295464 ] 

Jeremy Egenberger commented on THRIFT-4230:
-------------------------------------------

Thanks [~chetsky@gmail.com] and [~jking3], it turns out we were having a completely unrelated issue, actually it was a security tool properly detecting a vulnerability in our Thrift usage. I was grasping at straws thinking this bug was related to our problem and hence was looking for more information to confirm. It turns out I have no new information to contribute since my bug was not this bug.

> 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)