[
https://issues.apache.org/jira/browse/HBASE-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487500#comment-13487500
]
stack commented on HBASE-7070:
------------------------------
[~zjushch] Yes. Good catch.
I don't like that we are adding new max retry loop up in ClientScanner. We
have enough retrying and loops of retries already in the client.
The case you describe is a little pathological. Is it every going to succeed?
Not how you paint it. Should we retry if OutOfOrderException only, and retry
once only rather than some maximum retries number?
Good stuff.
> Scanner may retry forever after HBASE-5974
> -------------------------------------------
>
> Key: HBASE-7070
> URL: https://issues.apache.org/jira/browse/HBASE-7070
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.96.0
> Reporter: chunhui shen
> Assignee: chunhui shen
> Fix For: 0.96.0
>
> Attachments: HBASE-7070.patch
>
>
> After the patch of HBASE-5974
> Suppose The process is as the following:
> 1.A next request is very large, so first time it is failed because of timeout
> 2.The second time it is failed again because of
> CallSequenceOutOfOrderException
> 3.We will retry this next request again after reset scanner, so it is also
> very large and failed again because of timeout
> 4.CallSequenceOutOfOrderException again
> 5.Repeated the above forever...
> See the comment in HBASE-5974 for more
> https://issues.apache.org/jira/browse/HBASE-5974?focusedCommentId=13486658&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13486658
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
