Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 31 Oct 2012 05:37:13 +0000 (UTC)
From: "chunhui shen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <262261375.49185.1351661833325.JavaMail.jiratomcat@arcas>
In-Reply-To: <384201516.43648.1351585212357.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HBASE-7070) Scanner may retry forever  after
 HBASE-5974
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

chunhui shen updated HBASE-7070:
--------------------------------

    Attachment: HBASE-7070v5.patch

Attaching patchV5:
retry only once if OutOfOrderScannerNextException as Stack's comment
                
> 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