[
https://issues.apache.org/jira/browse/HBASE-14196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694819#comment-14694819
]
Hudson commented on HBASE-14196:
--------------------------------
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1032 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1032/])
HBASE-14196 Thrift server idle connection timeout issue (Vladimir Rodionov)
(apurtell: rev a705a7484637c94c1d4c3555c3888cf3908611ce)
*
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java
*
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/IncrementCoalescer.java
> 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.3.0, 1.1.3
>
> 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)
