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

Hudson commented on HBASE-18295:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3358 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/3358/])
HBASE-18295  The result contains the cells across different rows (chia7712: rev 
d215cb495085c5b7e5b27ce2ffdb6c4b4a90b95f)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStore.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java


>  The result contains the cells across different rows
> ----------------------------------------------------
>
>                 Key: HBASE-18295
>                 URL: https://issues.apache.org/jira/browse/HBASE-18295
>             Project: HBase
>          Issue Type: Bug
>          Components: Scanners
>    Affects Versions: 1.3.0, 1.3.1, 2.0.0-alpha-1
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Blocker
>             Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 2.0.0-alpha-2
>
>         Attachments: HBASE-18295.branch-1.3.v0.patch, 
> HBASE-18295.branch-1.3.v1.patch, HBASE-18295.branch-1.3.v2.patch, 
> HBASE-18295.branch-1.v0.patch, HBASE-18295.branch-1.v1.patch, 
> HBASE-18295.branch-1.v1.patch, HBASE-18295.branch-1.v1.patch, 
> HBASE-18295.branch-1.v2.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch, 
> HBASE-18295.v2.patch, HBASE-18295.v2.patch, HBASE-18295.v3.patch
>
>
> From the [flaky 
> dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html]
> If we use the cell which won't be flushed into disk as the top cell to reopen 
> the scanners, the new top cell will change. If the new top cell is in 
> different row, the matcher will reset, and then matcher will accept the new 
> top cell...
> The TestStore# testFlushBeforeCompletingScan reproduces the bug.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to