[
https://issues.apache.org/jira/browse/HBASE-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220370#comment-13220370
]
stack commented on HBASE-5492:
------------------------------
bq. Your question can be converted into who is responsible for refreshing of
cachedRegionLocations?
You can do that. Its done as the HTable runs but there are no guarantees the
cache is complete at any one time, right?
Change + if (tableLocations.size() == 0) { to tableLocations.isEmpty()..
the former can be costly compared.
So, IIUC, you are asking to pull all region locations local in locateRegions?
Does this get all table regions? Or just the configured next ten regions?
+ prefetchRegionCache(tableName, null);
> 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
