Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 9 Jan 2015 22:29:34 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12766556.1420842436000.51369.1420842574549@Atlassian.JIRA>
In-Reply-To: <JIRA.12766556.1420842436000@Atlassian.JIRA>
References: <JIRA.12766556.1420842436000@Atlassian.JIRA>
 <JIRA.12766556.1420842436545@arcas>
Subject: [jira] [Commented] (HBASE-12835) HBASE-12422 changed new
 HTable(Configuration) to not use managed Connections anymore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-12835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271978#comment-14271978 ] 

Enis Soztutar commented on HBASE-12835:
---------------------------------------

One example is TestAcidGuarantees. When run with 
{code}
hbase org.apache.hadoop.hbase.TestAcidGuarantees -Dmillis=60000 -DnumWriters=150 -DnumGetters=50 -DnumScanners=15 -DnumUniqueRows=25 2>&1 | tee /tmp/acid.log
{code}
It actually launches hundreds of connections because it uses {{new HTable(Conf, TableName)}}. 

> HBASE-12422 changed new HTable(Configuration) to not use managed Connections anymore
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-12835
>                 URL: https://issues.apache.org/jira/browse/HBASE-12835
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 1.0.0, 1.1.0
>
>
> While debugging something else, I've noticed that HBASE-12422 changed it so that new HTable(Configuration, TableName) is not using managed connections anymore. 
> I thought the plan was to keep new HTable(Conf, TableName) to still use managed connections, but allow the new APIs to have un-managed connections. With HBASE-12422, there is a big compatibility change for used of the HTable interface that suddenly they will be launching connections per HTable instance which is a behavioral change and expensive (with all the meta cache, zk threads, thread pool, etc). I fear that this will catch unsuspecting users by surprise, that is why I think we should revert back to the deprecated behavior for 1.0. For master we do not need to make the change, but document it. 
> [~sduskis], [~saint.ack@gmail.com], [~ndimiduk] what do you guys think?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)