[
https://issues.apache.org/jira/browse/HBASE-12266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172397#comment-14172397
]
James Estes commented on HBASE-12266:
-------------------------------------
Thanks for filing.
It looks like that was set to true due to a VERY similar issue
https://issues.apache.org/jira/browse/HBASE-7070 so that it would only
reset/retry for one rpc call. In my case though, the "reset/retry only for one
call" doesn't work because it will have a few successful rpc calls after the
reset (the earlier ones are getting a tiny amount of data, and then the super
slow rpc happens on about the 4th rpc).
Looking a bit further down, there is logic for the UnknownScannerException that
will make sure we're not over the scannerTimeout. Should that logic maybe be
used for all exceptions? Maybe even at the top of the while loop, but I think
changing it only in the exception case would fix my issue...it would stop
retrying after 60s (the default for scannerTimeout).
> Slow Scan can cause dead loop in ClientScanner
> -----------------------------------------------
>
> Key: HBASE-12266
> URL: https://issues.apache.org/jira/browse/HBASE-12266
> Project: HBase
> Issue Type: Bug
> Components: Scanners
> Affects Versions: 0.96.0
> Reporter: Qiang Tian
> Priority: Minor
> Attachments: HBASE-12266-master.patch
>
>
> see http://search-hadoop.com/m/DHED45SVsC1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
