Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2BA1318571 for ; Wed, 7 Oct 2015 02:37:01 +0000 (UTC) Received: (qmail 24150 invoked by uid 500); 7 Oct 2015 02:36:27 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 24087 invoked by uid 500); 7 Oct 2015 02:36:27 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 23738 invoked by uid 99); 7 Oct 2015 02:36:26 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2015 02:36:26 +0000 Date: Wed, 7 Oct 2015 02:36:26 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-14497) Reverse Scan threw StackOverflow caused by readPt checking MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946153#comment-14946153 ] Hudson commented on HBASE-14497: -------------------------------- FAILURE: Integrated in HBase-1.3-IT #215 (See [https://builds.apache.org/job/HBase-1.3-IT/215/]) HBASE-14497 Reverse Scan threw StackOverflow caused by readPt checking (tedyu: rev 5e2db42d680f35c1f0a345344a6555ea319d870b) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileScanner.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultMemStore.java > Reverse Scan threw StackOverflow caused by readPt checking > ---------------------------------------------------------- > > Key: HBASE-14497 > URL: https://issues.apache.org/jira/browse/HBASE-14497 > Project: HBase > Issue Type: Bug > Affects Versions: 2.0.0, 0.98.14, 1.3.0 > Reporter: Yerui Sun > Assignee: Yerui Sun > Fix For: 2.0.0, 1.3.0 > > Attachments: 14497-branch-1-v6.patch, 14497-master-v6.patch, HBASE-14497-0.98.patch, HBASE-14497-branch-1-v2.patch, HBASE-14497-branch-1-v3.patch, HBASE-14497-branch-1-v6.patch, HBASE-14497-branch-1.patch, HBASE-14497-master-v2.patch, HBASE-14497-master-v3.patch, HBASE-14497-master-v3.patch, HBASE-14497-master-v4.patch, HBASE-14497-master-v5.patch, HBASE-14497-master.patch > > > I met stack overflow error in StoreFileScanner.seekToPreviousRow using reversed scan. I searched and founded HBASE-14155, but it seems to be a different reason. > The seekToPreviousRow will fetch the row which closest before, and compare mvcc to the readPt, which acquired when scanner created. If the row's mvcc is bigger than readPt, an recursive call of seekToPreviousRow will invoked, to find the next closest before row. > Considering we created a scanner for reversed scan, and some data with smaller rows was written and flushed, before calling scanner next. When seekToPreviousRow was invoked, it would call itself recursively, until all rows which written after scanner created were iterated. The depth of recursive calling stack depends on the count of rows, the stack overflow error will be threw if the count of rows is large, like 10000. -- This message was sent by Atlassian JIRA (v6.3.4#6332)