hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8136) coprocessor service requires .meta. to be available all the time.
Date Mon, 18 Mar 2013 16:20:16 GMT

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

Andrew Purtell commented on HBASE-8136:
---------------------------------------

Close this as a dup N?
                
> coprocessor service requires .meta. to be available all the time.
> -----------------------------------------------------------------
>
>                 Key: HBASE-8136
>                 URL: https://issues.apache.org/jira/browse/HBASE-8136
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, Coprocessors
>    Affects Versions: 0.96.0
>            Reporter: nkeywal
>            Priority: Minor
>
> HTable#getRegionLocations does not use a cache: all the calls to this function go to
.META.
> So:
> - we're missing an opportunity to reuse/update the location cache in the HConnection.
> - this method is called by the coprocessor service. So, for people using this features,
they have .meta. on their execution path, and it's not good for performances, scalability
and reliability.
> I'm not totally clear on the fix. I think it should be possible to use the cache to see
if we have all regions for the table. But it means we won't always have the last version when
calling getRegionLocations.
> Any thought on this?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message