You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/03/15 18:41:00 UTC
[jira] [Resolved] (HBASE-18216) [AMv2] Workaround for HBASE-18152,
corrupt procedure WAL
[ https://issues.apache.org/jira/browse/HBASE-18216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-18216.
---------------------------
Resolution: Fixed
Re-resolving. My backport trashed branch-1. Sorry about that [~apurtell] (Just saw the damage I did..). So, Andrew reopened this to revert from branch-1. The workarounds are in branch-2.
550b6c585e HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL; ADDENDUM
0b43353bf7 HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL
Re-resolving.
> [AMv2] Workaround for HBASE-18152, corrupt procedure WAL
> --------------------------------------------------------
>
> Key: HBASE-18216
> URL: https://issues.apache.org/jira/browse/HBASE-18216
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Affects Versions: 2.0.0
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-18216.branch-1.001.patch
>
>
> Let me commit workaround for the issue up in HBASE-18152, corruption in the master wal procedure files. Testing on cluster shows it helps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)