hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18152) [AMv2] Corrupt Procedure WAL file; procedure data stored out of order
Date Wed, 14 Jun 2017 08:09:00 GMT

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

Hudson commented on HBASE-18152:

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3192 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3192/])
HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL (stack: rev 0b43353bf76f19e020e2831691a832722b590915)
* (edit) hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALFormatReader.java
HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL; (stack: rev 550b6c585e0390bc80516e64df8bd1a3a6e10e23)
* (edit) hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALFormatReader.java

> [AMv2] Corrupt Procedure WAL file; procedure data stored out of order
> ---------------------------------------------------------------------
>                 Key: HBASE-18152
>                 URL: https://issues.apache.org/jira/browse/HBASE-18152
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Region Assignment
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: HBASE-18152.master.001.patch, pv2-00000000000000000036.log, pv2-00000000000000000047.log,
> I've seen corruption from time-to-time testing.  Its rare enough. Often we can get over
it but sometimes we can't. It took me a while to capture an instance of corruption. Turns
out we are write to the WAL out-of-order which undoes a basic tenet; that WAL content is ordered
in line w/ execution.
> Below I'll post a corrupt WAL.
> Looking at the write-side, there is a lot going on. I'm not clear on how we could write
out of order. Will try and get more insight. Meantime parking this issue here to fill data

This message was sent by Atlassian JIRA

View raw message