[
https://issues.apache.org/jira/browse/HBASE-16266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389464#comment-15389464
]
Phil Yang commented on HBASE-16266:
-----------------------------------
Thanks for reviewing.
{quote}
What is an example scenario that makes the below?
{quote}
At server if the scanner reaches size limit or time limit, partial result or
heartbeat will be responded to the client, then the client will send a new rpc
call until the client get at least a whole row and can return a Result to user.
So the total time of blocking on ResultScanner.next() depends on how many rpc
requests in loadCache() and may be longer than a single rpc timeout
> Do not throw ScannerTimeoutException when catch UnknownScannerException
> -----------------------------------------------------------------------
>
> Key: HBASE-16266
> URL: https://issues.apache.org/jira/browse/HBASE-16266
> Project: HBase
> Issue Type: Improvement
> Components: Client, Scanners
> Affects Versions: 1.1.5, 1.2.2
> Reporter: Phil Yang
> Assignee: Phil Yang
> Attachments: HBASE-16266-v1.patch, HBASE-16266-v2.patch,
> HBASE-16266-v3.patch
>
>
> Now in scanner we have heartbeat to prevent timeout. The time blocked on
> ResultScanner.next() may much longer than scanner timeout. So it is no need
> any more to throw ScannerTimeoutException when server throws
> UnknownScannerException, we can just reset the scanner like
> NotServingRegionException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
