hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15984) Given failure to parse a given WAL that was closed cleanly, replay the WAL.
Date Mon, 19 Sep 2016 19:38:21 GMT

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

Sean Busbey commented on HBASE-15984:

Since we're talking about data loss, I originally wanted to push this for all branches. I'm
fine leaving out the metrics additions on maintenance release lines if folks prefer, but I've
always interpreted the operational section of the compatibility promises as saying we wouldn't
remove metrics in a maintenance release rather than that we wouldn't add them.

> Given failure to parse a given WAL that was closed cleanly, replay the WAL.
> ---------------------------------------------------------------------------
>                 Key: HBASE-15984
>                 URL: https://issues.apache.org/jira/browse/HBASE-15984
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 2.0.0, 1.0.4, 1.4.0, 1.3.1, 1.1.7, 0.98.23, 1.2.4
>         Attachments: HBASE-15984.1.patch, HBASE-15984.2.patch
> subtask for a general work around for "underlying reader failed / is in a bad state"
just for the case where a WAL 1) was closed cleanly and 2) we can tell that our current offset
ought not be the end of parseable entries.

This message was sent by Atlassian JIRA

View raw message