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 Sat, 01 Jul 2017 07:03:03 GMT

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

Hudson commented on HBASE-18152:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-1.4 #796 (See [https://builds.apache.org/job/HBase-1.4/796/])
HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL (stack: rev 8ce3f49f8034417734ef1a3e6c624a601a22ace9)
* (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,
reading_bad_wal.patch
>
>
> 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
into.



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

Mime
View raw message