[
https://issues.apache.org/jira/browse/HBASE-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-15593:
------------------------------
Description: 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. (was: 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) is 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.)
> 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.1.0
> Reporter: Phil Yang
> Assignee: Phil Yang
>
> 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)
