[
https://issues.apache.org/jira/browse/HBASE-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HBASE-10357:
--------------------------------
Attachment: 10357-4.3.2.txt
bq. Can it happen that we try to close first, then open the scanner?
Yes there is some (rare) chance that this might happen. When this happens the
scanner on the server side will eventually get closed when the lease expires. I
think (and as discussed offline), let's leave it as is for now and if this
becomes a problem, we can think of ways to address it (like via additional
synchronization that will prevent close from getting called until scanner is
opened, etc.)
bq. Sorry, one thing I forgot to mention was that, whether or not we can make
the replicas transparent to the ClientScanner
I wanted to make the ClientScanner totally unaware of the replica logic as well
but at the same time didn't want to make the ScannerCallableWithReplicas more
complex than needed. So yes, there is some awareness of replicas in the
ClientScanner but it's minimal and it falls in line with the way ClientScanner
already handles scan exceptions. I have put in comments in the code explaining
what is being done in ClientScanner.
> Failover RPC's for scans
> ------------------------
>
> Key: HBASE-10357
> URL: https://issues.apache.org/jira/browse/HBASE-10357
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Reporter: Enis Soztutar
> Fix For: 0.99.0, hbase-10070
>
> Attachments: 10357-1.txt, 10357-2.txt, 10357-3.2.txt, 10357-3.txt,
> 10357-4.2.txt, 10357-4.3.1.txt, 10357-4.3.2.txt, 10357-4.3.txt, 10357-4.txt
>
>
> This is extension of HBASE-10355 to add failover support for scans.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
