[jira] [Commented] (HBASE-15593) Time limit of scanning should be offered by client

["Nick Dimiduk (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265884#comment-15265884 ] 

Nick Dimiduk commented on HBASE-15593:
--------------------------------------

This sounds like a good one to land, though based on my skim, is more of an improvement than a bug fix. Think we should drop it from the maintenance-mode branches. You fellas think otherwise?

> Time limit of scanning should be offered by client
> --------------------------------------------------
>
>                 Key: HBASE-15593
>                 URL: https://issues.apache.org/jira/browse/HBASE-15593
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 1.1.4
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2
>
>         Attachments: HBASE-15593-branch-1-v1.patch, HBASE-15593-branch-1-v2.patch, HBASE-15593-branch-1-v3.patch, HBASE-15593-branch-1.1-v1.patch, HBASE-15593-branch-1.1-v2.patch, HBASE-15593-branch-1.1-v3.patch, HBASE-15593-branch-1.2-v1.patch, HBASE-15593-branch-1.2-v2.patch, HBASE-15593-branch-1.2-v3.patch, HBASE-15593-v1.patch, HBASE-15593-v2.patch, HBASE-15593-v3.patch, HBASE-15593-v4.patch, HBASE-15593-v5.patch, HBASE-15593-v6.patch, HBASE-15593-v7.patch
>
>
> In RSRpcServices.scan, we will set a time limit equaling to Math.min(scannerLeaseTimeoutPeriod, rpcTimeout) / 2, and will response heartbeat message if we reach this limit. However, two timeout settings (hbase.client.scanner.timeout.period and hbase.rpc.timeout) are read from RS's configure, which may be different from client's. If client's setting is much less than server's, there may still be timeout at client side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)