hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heng Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14361) Investigate unused connection objects
Date Sun, 06 Sep 2015 08:47:46 GMT

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

Heng Chen commented on HBASE-14361:
-----------------------------------

In standalone mode,  there are two RS,   So we can see there are two {{ConnectionImplementation}}
created by {{org.apache.hadoop.hbase.replication.regionserver.ReplicationSink.<init>(ReplicationSink.java:91)}}
and 
{{org.apache.hadoop.hbase.regionserver.HRegionServer.createClusterConnection(HRegionServer.java:686)}}

> Investigate unused connection objects
> -------------------------------------
>
>                 Key: HBASE-14361
>                 URL: https://issues.apache.org/jira/browse/HBASE-14361
>             Project: HBase
>          Issue Type: Task
>          Components: Client
>            Reporter: Nick Dimiduk
>         Attachments: hmaster.log
>
>
> Over on HBASE-12911 I have a patch that registers Connection instances with the metrics
system. In both standalone server and tll client applications, I was surprised to see multiple
connection objects showing up that are unused. These are pretty heavy objects, including lots
of client threads for the batch pool. We should track these down and remove them -- if they're
not some kind of phantom artifacts of my WIP patch over there.



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

Mime
View raw message