hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14196) Thrift server idle connection timeout issue
Date Thu, 08 Oct 2015 00:17:27 GMT

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

stack commented on HBASE-14196:
-------------------------------

[~vrodionov] How did this issue manifest itself? [~syuanjiang] just sent me here from HBASE-14533
just as I was trying to reproduce the issue locally (was seen on a server internally... but
couldn't figure the why nor reproduce with simple test).  Does HBASE-14533 look like what
you were seeing?  Thanks.

> Thrift server idle connection timeout issue
> -------------------------------------------
>
>                 Key: HBASE-14196
>                 URL: https://issues.apache.org/jira/browse/HBASE-14196
>             Project: HBase
>          Issue Type: Bug
>          Components: Thrift
>    Affects Versions: 0.98.13, 1.1.1, 1.0.1.1, 1.1.0.1
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>             Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>
>         Attachments: HBASE-14196.patch
>
>
> When idle connection get cleaned from Thrift server, underlying table instances are still
cached in a thread local cache.
> This is the antipattern. Table objects are lightweight and should not be cached, besides
this, underlying connections can be closed by periodic connection cleaner chore (ConnectionCache)
and cached table instances may become invalid. This is Thrift1 specific issue. Thrift2 is
OK.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message