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

Hudson commented on HBASE-23741:
--------------------------------

Results for branch master
        [build #1676 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1676/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1676//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1676//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1676//JDK8_Nightly_Build_Report_(Hadoop3)/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1676//JDK11_Nightly_Build_Report/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for 
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1676//artifact/output-integration/hadoop-2.log].
 (note that this means we didn't run on Hadoop 3)


> Data loss when WAL split to HFile enabled
> -----------------------------------------
>
>                 Key: HBASE-23741
>                 URL: https://issues.apache.org/jira/browse/HBASE-23741
>             Project: HBase
>          Issue Type: Bug
>          Components: MTTR
>    Affects Versions: 3.0.0, 2.3.0
>            Reporter: Pankaj Kumar
>            Assignee: Guanghao Zhang
>            Priority: Blocker
>             Fix For: 3.0.0, 2.3.0, 2.4.0
>
>
> Very simple steps as below,
> 1. Create table with 1 region
> 2. Insert 1 record 
> 3. Flush the table 
> 4. Scan table and observe timestamp of the inserted row
> 5. Insert same row key with same timestamp as previously inserted but with 
> different value
> 6. Kill -9 RS where table region is online
> 7. Start RS
> Scan the table and check the result, latest cell must be returned.
> Thanks [~sreenivasulureddy] for finding this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to