Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 29 Feb 2012 16:31:58 +0000 (UTC)
From: "stack (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1413222858.3549.1330533118168.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <42387391.3475.1330532517556.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5492) Caching StartKeys and EndKeys of
 Regions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-5492:
------------------------------

Once filled, how does the cache of table locations get refreshed if a table region splits?
                
> Caching StartKeys and EndKeys of Regions
> ----------------------------------------
>
>                 Key: HBASE-5492
>                 URL: https://issues.apache.org/jira/browse/HBASE-5492
>             Project: HBase
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 0.92.0
>         Environment: all
>            Reporter: honghua zhu
>             Fix For: 0.92.1
>
>         Attachments: HBASE-5492.patch
>
>
> Each call for HTable.getStartEndKeys will read meta table.
> In particular, 
> in the case of client side multi-threaded concurrency statistics, 
> we must call HTable.coprocessorExec== > getStartKeysInRange ==> getStartEndKeys,
> resulting in the need to always scan the meta table.
> This is not necessary,
> we can implement the HConnectionManager.HConnectionImplementation.locateRegions(byte[] tableName) method,
> then, get the StartKeys and EndKeys from the cachedRegionLocations of HConnectionImplementation.
> Combined with https://issues.apache.org/jira/browse/HBASE-5491, can improve the performance of statistical

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira