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-13895) DATALOSS: Region assigned before WAL replay when abort
Date Fri, 18 Mar 2016 22:30:33 GMT

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

stack updated HBASE-13895:
    Release Note: If the master went to assign a region concurrent with a RegionServer abort,
the returned RegionServerAbortedException was being handled as though the region had been
cleanly offlined so assign was allowed proceed. If the region was opened in its new location
before WAL replay completion, the replayed edits were ignored, worst case, or were later played
over the top of edits that had come in since open and so susceptible to overwrite. In either

> DATALOSS: Region assigned before WAL replay when abort
> ------------------------------------------------------
>                 Key: HBASE-13895
>                 URL: https://issues.apache.org/jira/browse/HBASE-13895
>             Project: HBase
>          Issue Type: Bug
>          Components: Recovery, Region Assignment, wal
>    Affects Versions: 1.2.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0, 1.2.0, 1.1.2
>         Attachments: 13895.branch-1.2.txt, 13895.master.addendum2.txt, 13895.master.patch,
hbase-13895_addendum-master.patch, hbase-13895_addendum.patch, hbase-13895_addendum3-branch-1.1.patch,
hbase-13895_addendum3-branch-1.patch, hbase-13895_addendum3-master.patch, hbase-13895_v1-branch-1.1.patch
> Opening a place holder till finish analysis.
> I have dataloss running ITBLL at 3B (testing HBASE-13877). Most obvious culprit is the
double-assignment that I can see.

This message was sent by Atlassian JIRA

View raw message