Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 9 Sep 2015 20:45:46 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12861648.1441307105000.294592.1441831546359@Atlassian.JIRA>
In-Reply-To: <JIRA.12861648.1441307105000@Atlassian.JIRA>
References: <JIRA.12861648.1441307105000@Atlassian.JIRA>
 <JIRA.12861648.1441307105289@arcas>
Subject: [jira] [Updated] (HBASE-14361) ReplicationSink should create
 Connection instances lazily
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nick Dimiduk updated HBASE-14361:
---------------------------------
    Fix Version/s: 1.1.3
                   1.0.3
                   0.98.15
                   1.3.0
                   1.2.0
                   2.0.0

> 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.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)