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-14361) Investigate unused connection objects
Date Wed, 09 Sep 2015 05:21:46 GMT

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

stack commented on HBASE-14361:
-------------------------------

Nice [~chenheng]

Standalone mode should have one RS only I'd say, not two.

That Replication puts up a connection to nowhere (because in standalone, there is no configured
sink... Would be good if Replication didn't put up a Connection till it had something to Connect
to.


> 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