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

Hudson commented on HBASE-22340:
--------------------------------

Results for branch branch-2
        [build #1861 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1861/]: 
(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/branch-2/1861//General_Nightly_Build_Report/]




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


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


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


> Corrupt KeyValue is silently ignored
> ------------------------------------
>
>                 Key: HBASE-22340
>                 URL: https://issues.apache.org/jira/browse/HBASE-22340
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>    Affects Versions: 3.0.0, 2.2.0, 2.1.2, 2.0.4
>            Reporter: Peter Somogyi
>            Assignee: Peter Somogyi
>            Priority: Critical
>             Fix For: 3.0.0, 2.2.0, 2.0.6, 2.1.5
>
>
> When a KeyValue is constructed from a corrupt byte array then 
> IllegalArgumentException is thrown with a detailed message where the issue is 
> in the array. This is part of a sanity check introduced in HBASE-21401.
> However, this is not logged at this time and the exception goes up to 
> ProtobufLogReader.readNext where it is caught, wrapped into EOFException and 
> the processing of the current WAL file is stopped.
> There is only a TRACE level log message that could indicate if something went 
> wrong.
> This will cause data loss without log message not just for the single 
> corrupted KV but for the rest of the WAL file.



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

Reply via email to