[
https://issues.apache.org/jira/browse/HBASE-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994036#comment-13994036
]
Devaraj Das commented on HBASE-10357:
-------------------------------------
bq. Should this be called hbase.client.primaryCallTimeout.scan? The get and
multiGet are named like that. Is this because the timeout applies to replica
requests for next call as well?
In the scan case, when a replica (be it primary or not) is latched onto, we try
to get as much as possible from that replica (without switching to the primary
in the middle of the scan). We'd wait for the 1000 ms irrespective of whether
the replica is primary or not. Hence the name doesn't have "primary" in it..
> 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
>
> Attachments: 10357-1.txt, 10357-2.txt, 10357-3.2.txt, 10357-3.txt,
> 10357-4.2.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)
