[
https://issues.apache.org/jira/browse/HBASE-14196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948768#comment-14948768
]
stack commented on HBASE-14196:
-------------------------------
Thank you [~vrodionov] I tried various things .... many threads waiting then
mutating in the hope of tripping the timedout connection with chore time set
down -- a version of which I posted here
https://issues.apache.org/jira/secure/attachment/12764610/test.patch -- but
was only able to repro the issue w/ much manual intervention... I'll keep at
it.... thinking on it, I may have been testing against a version of hbase that
had your fix here. Let me back up some versions.
Regardless, this is a nice find. Good one.
> 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)
