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

Hudson commented on HBASE-21838:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1665//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/branch-2/1665//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/branch-2/1665//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


(/) {color:green}+1 client integration test{color}


> Create a special ReplicationEndpoint just for verifying the WAL entries are 
> fine
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-21838
>                 URL: https://issues.apache.org/jira/browse/HBASE-21838
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication, wal
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.3.0
>
>         Attachments: HBASE-21838-v1.patch, HBASE-21838.patch
>
>
> This is a missing part in our ITBLL. We can config a dummy replication 
> endpoint which replicates nothing but only reads and verifies that all the 
> wal files are readable and the entries are all fine.
> With this I think it will be much easier to catch the problem in the parent 
> issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to