You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2012/08/09 07:32:20 UTC

[jira] [Resolved] (HBASE-6522) Expose locks and leases to Coprocessors

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

Lars Hofhansl resolved HBASE-6522.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.94.2
                   0.96.0
     Hadoop Flags: Reviewed

At the same time we can tackle this in another jira when it turns out to actually be a problem. As it stands in 0.94 all leases take default leasePeriod configured for this region server.
                
> Expose locks and leases to Coprocessors
> ---------------------------------------
>
>                 Key: HBASE-6522
>                 URL: https://issues.apache.org/jira/browse/HBASE-6522
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: 6522-v2.txt, 6522.txt
>
>
> Currently it is not possible for CP to implement any of checkAndMutate type operations, because coprocessor have no way create a lock, because getLock is private HRegion (interestingly ReleaseLock is public).
> In addition it would nice if Coprocessor could hook into the RegionServers' Lease management.
> Here I propose two trivial changes:
> # Make HRegion.getLock public
> # Add {code}Leases getLeases(){code} to RegionServerServices (and hence to HRegionServer)

--
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