Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B48BE106F1 for ; Sun, 17 Nov 2013 03:07:24 +0000 (UTC) Received: (qmail 2885 invoked by uid 500); 17 Nov 2013 03:07:21 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 2858 invoked by uid 500); 17 Nov 2013 03:07:20 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 2850 invoked by uid 99); 17 Nov 2013 03:07:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Nov 2013 03:07:20 +0000 Date: Sun, 17 Nov 2013 03:07:19 +0000 (UTC) From: "Anil Gupta (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-9984) AggregationClient creates a new Htable, HConnection,and ExecutorService in every CP call. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anil Gupta updated HBASE-9984: ------------------------------ Description: At present AggregationClient takes Conf in constructor and create a new Htable instance on every method calls. The constructor of HTable used in AggregationClient is very heavy as it creates a new HConnection and ExecutorService. Above mechanism is not convenient where the Application is managing HTable, HConnection, ExecutorService by itself. So, i propose 1# AggregationClient should provide an additional constructor: AggregationClient(HTable) 2# Provide methods that takes Htable. In this way we can avoid creation of Htable, HConnection,and ExecutorService in every CP call. was: At present AggregationClient takes Conf in constructor and create a new Htable instance on every method calls. The constructor of HTable used in AggregationClient is very heavy as it creates a new HConnection and ExecutorService. Above mechanism is not convenient where the Application is managing HTable, HConnection, ExecutorService by itself. So, i propose 1# AggregationClient should provide an additional constructor or: AggregationClient(HTable) 2# Provide methods that takes Htable. In this way we can avoid creation of Htable, HConnection,and ExecutorService in every CP call. > AggregationClient creates a new Htable, HConnection,and ExecutorService in every CP call. > ----------------------------------------------------------------------------------------- > > Key: HBASE-9984 > URL: https://issues.apache.org/jira/browse/HBASE-9984 > Project: HBase > Issue Type: Improvement > Components: Client, Coprocessors > Affects Versions: 0.94.13 > Reporter: Anil Gupta > Priority: Minor > Labels: aggregate, client, coprocessors, hbase > > At present AggregationClient takes Conf in constructor and create a new Htable instance on every method calls. The constructor of HTable used in AggregationClient is very heavy as it creates a new HConnection and ExecutorService. > Above mechanism is not convenient where the Application is managing HTable, HConnection, ExecutorService by itself. So, i propose > 1# AggregationClient should provide an additional constructor: AggregationClient(HTable) > 2# Provide methods that takes Htable. > In this way we can avoid creation of Htable, HConnection,and ExecutorService in every CP call. -- This message was sent by Atlassian JIRA (v6.1#6144)