[
https://issues.apache.org/jira/browse/HBASE-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159793#comment-16159793
]
Chia-Ping Tsai commented on HBASE-13333:
----------------------------------------
The patch for HBASE-13333 addes the renewLease() to different classes.
* branch-1 : AbstractClientScanner#renewLease()
* master : ResultScanner#renewLease()
And then HBASE-17584 moved the renewLease() from AbstractClientScanner to
ResultScanner for branch-1.
In short. the location of renewLease() is shown below.
* branch-1.3/branch-1.2 : AbstractClientScanner (introduced by HBASE-13333)
* branch-1/branch-1.4 : ResultScanner (introduced by HBASE-17584)
* master/branch-2 : ResultScanner (introduced by HBASE-13333)
> Renew Scanner Lease without advancing the RegionScanner
> -------------------------------------------------------
>
> Key: HBASE-13333
> URL: https://issues.apache.org/jira/browse/HBASE-13333
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
> Attachments: 13333-0.98.txt, 13333-master.txt
>
>
> We have a usecase (for Phoenix) where we want to let the server know that the
> client is still around. Like a client-side heartbeat.
> Doing a full heartbeat is complicated, but we could add the ability to make
> scanner call with caching set to 0. The server already does the right thing
> (it renews the lease, but does not advance the scanner).
> It looks like the client (ScannerCallable) also does the right thing. We
> cannot break ResultScanner before HBase 2.0, but we can add a renewLease()
> method to AbstractClientScaner. Phoenix (or any other caller) can then cast
> to ClientScanner and call that method to ensure we renew the lease on the
> server.
> It would be a simple and fully backwards compatible change. [~giacomotaylor]
> Comments?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
