[ https://issues.apache.org/jira/browse/HBASE-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739601#comment-14739601 ]
stack commented on HBASE-14361: ------------------------------- [~lhofhansl] Good point. Yes. In batch, for sure. Let me revert until fixed. Thanks. > ReplicationSink should create Connection instances lazily > --------------------------------------------------------- > > Key: HBASE-14361 > URL: https://issues.apache.org/jira/browse/HBASE-14361 > Project: HBase > Issue Type: Task > Components: Replication > Reporter: Nick Dimiduk > Assignee: Heng Chen > Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.15, 1.0.3, 1.1.3 > > Attachments: HBASE-14361-0.98.patch, HBASE-14361.patch, 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)