Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Nov 2013 04:43:17 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12678117.1383869463345.40584.1383885797402@arcas>
In-Reply-To: <JIRA.12678117.1383869463345@arcas>
References: <JIRA.12678117.1383869463345@arcas>
Subject: [jira] [Updated] (HBASE-9917) Fix it so Default Connection Pool
 does not spin up max threads even when not needed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-9917:
-------------------------

    Attachment: 9917.txt

Retry.  Starts w/ zero threads.  Let the client ramp up rather than have 8 idle when nothing going on.

> Fix it so Default Connection Pool does not spin up max threads even when not needed
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-9917
>                 URL: https://issues.apache.org/jira/browse/HBASE-9917
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.98.0, 0.96.1
>
>         Attachments: 9917.txt, pool.txt
>
>
> Testing, I noticed that if we use the HConnection executor service as opposed to the executor service that is created when you create an HTable without passing in a connection: i.e
> HConnectionManager.createConnection(config).getTable(tableName)
> vs
> HTable(config, tableName)
> ... then we will spin up the max 256 threads and they will just hang out though not being used.
> We are encouraging HConnection#getTable over new HTable so worth fixing.


--
This message was sent by Atlassian JIRA
(v6.1#6144)