[ https://issues.apache.org/jira/browse/HBASE-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487569#comment-13487569 ]
stack commented on HBASE-7070: ------------------------------ Should it be a flag that gets set when we are retrying because of a OutOfOrderScannerNextException? The flag, called retryAfterOutOfOrderException or some such then stays set while we retry. If we get a OutOfOrderScannerNextException again, we fail with an exception saying failed after retry. If next succeeds, flag is cleared. When you have it like this counting attempts, it is a little confusing I think. We will go around and around if we are getting socket timeouts? > 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, HBASE-7070v2.patch, > HBASE-7070v3.patch, HBASE-7070v4.patch, HBASE-7070v5.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