[ https://issues.apache.org/jira/browse/HBASE-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745709#comment-14745709 ]
Hudson commented on HBASE-14361: -------------------------------- SUCCESS: Integrated in HBase-1.2-IT #146 (See [https://builds.apache.org/job/HBase-1.2-IT/146/]) HBASE-14361 ReplicationSink should create Connection instances lazily (stack: rev 303e49e89a7eeda9c23a939e729927997f97dda9) * hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSink.java > 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, 1.0.3, 1.1.3 > > Attachments: 14361.v3.txt, 14361.v3.txt, 14361.v3.txt, 14361.v3.txt, > HBASE-14361-0.98.patch, HBASE-14361.patch, HBASE-14361_v1.patch, > HBASE-14361_v2.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)