You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2015/10/04 06:57:26 UTC

[jira] [Commented] (HBASE-14549) Simplify scanner stack reset logic

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

Lars Hofhansl commented on HBASE-14549:
---------------------------------------

TestAtomicOperation passes multiple runs (it mixes flushes and compaction with active scanning)

> Simplify scanner stack reset logic
> ----------------------------------
>
>                 Key: HBASE-14549
>                 URL: https://issues.apache.org/jira/browse/HBASE-14549
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>         Attachments: 14549-0.98.txt
>
>
> Looking at the code, I find that the logic is unnecessarily complex.
> We indicate in updateReaders that the scanner stack needs to be reset. Than almost all store scanner (and derived classes) methods need to check and actually reset the scanner stack.
> Compaction are rare, we should reset the scanner stack in update readers, and hence avoid needing to check in all methods.
> Patch forthcoming.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)