hbase-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HBASE-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-18152:
    Attachment: pv2-00000000000000000036.log

Another corruption form. Trying to figure it.

> [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-17537.master.002.patch, 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

This message was sent by Atlassian JIRA

View raw message