You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "nkeywal (JIRA)" <ji...@apache.org> on 2013/03/18 17:30:17 UTC

[jira] [Resolved] (HBASE-8136) coprocessor service requires .meta. to be available all the time.

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

nkeywal resolved HBASE-8136.
----------------------------

      Resolution: Duplicate
    Release Note: HBASE-6870 

And the good news if that there is already a patch for HBASE-6870 :-).
                
> 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