hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chunhui shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14497) Reverse Scan threw StackOverflow caused by readPt checking
Date Tue, 29 Sep 2015 02:04:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934483#comment-14934483

chunhui shen commented on HBASE-14497:

Good catch. [~sunyerui]
MemstoreScanner should have the same problem, could you fix it ?
The current solution in patch is good for me.


> 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
>         Attachments: HBASE-14497-0.98.patch, HBASE-14497-branch-1-v2.patch, HBASE-14497-branch-1.patch,
HBASE-14497-master-v2.patch, HBASE-14497-master-v3.patch, HBASE-14497-master-v3.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

View raw message