[jira] [Updated] (HBASE-12437) HLogFactory does not allow fall back of custom WALReader in case of failure to read WAL logs due to upgrade/migrate of hbase

["Enoch Hsu (JIRA)" <ji...@apache.org>]

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

Enoch Hsu updated HBASE-12437:
------------------------------
    Summary: HLogFactory does not allow fall back of custom WALReader in case of failure to read WAL logs due to upgrade/migrate of hbase  (was: HLogFactory should allow multiple custom WAL readers to be specified in case WAL reader fails instead of throwing InvalidProtocolBufferReaderException)

> HLogFactory does not allow fall back of custom WALReader in case of failure to read WAL logs due to upgrade/migrate of hbase
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-12437
>                 URL: https://issues.apache.org/jira/browse/HBASE-12437
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>    Affects Versions: 0.96.0, 0.98.4
>            Reporter: Enoch Hsu
>            Assignee: Enoch Hsu
>             Fix For: 1.0.0, 0.98.4
>
>         Attachments: HBASE_12437.patch
>
>
> The HLogFactory createReader function allows the user to create their own reader and just assumes that the reader will work correctly.
> In the case the user accidentally uses an incorrect reader and gets an InvalidProtocolBufferReaderException, HBase should have a safeguard to still allow HBase functions to execute.
> I propose that in this case HBase should default to the standard HBase readers.(ProtobufLogReader or  SequenceFIleLogReader)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)