You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vladimir Rodionov (JIRA)" <ji...@apache.org> on 2015/08/07 20:12:47 UTC

[jira] [Updated] (HBASE-14195) Closed connections are not removed from ConnectionCache (Thrift, REST)

     [ https://issues.apache.org/jira/browse/HBASE-14195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Rodionov updated HBASE-14195:
--------------------------------------
    Description: 
There is the issue with ConnectionCache (used to cache connections in Thrift and REST servers) chore implementation when closed connection is not removed from a cache.

Thrift server is affected most because it has local thread cache of Table instances and it does not check if Table instance is invalid (due to closed underlying connection) and it can't do it - no API.  

  was:
There is the issue with ConnectionCache (used to cache connections in Thrift and REST servers) chore implementation when closed connection is not removed from cache.

Thrift server is affected most because it has local thread cache of Table instances and it does not check if Table instance is invalid (due to closed underlying connection) and it can't do it - no API.  


> Closed connections are not removed from ConnectionCache (Thrift, REST)
> ----------------------------------------------------------------------
>
>                 Key: HBASE-14195
>                 URL: https://issues.apache.org/jira/browse/HBASE-14195
>             Project: HBase
>          Issue Type: Bug
>          Components: REST, 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
>
>
> There is the issue with ConnectionCache (used to cache connections in Thrift and REST servers) chore implementation when closed connection is not removed from a cache.
> Thrift server is affected most because it has local thread cache of Table instances and it does not check if Table instance is invalid (due to closed underlying connection) and it can't do it - no API.  



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