[
https://issues.apache.org/jira/browse/HBASE-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HBASE-21817:
-------------------------------------
Description:
See HBASE-21601 for context.
I looked at the code a bit but it will take a while to understand, so for now
I'm going to mitigate it by handling such cases like any other corrupted WAL
(via either skipErrors or CorruptedHLog exception)
was:
See HBASE-21601 for context.
I looked at the code a bit but it will take a while to understand, so for now
I'm going to mitigate it by skipping such records. Given that this record is
bogus, and the lengths are intact, for this scenario it's safe to do so.
However, it's possible I guess to have a bug where skipping such record would
lead to data loss. Regardless, failure to split the WAL will lead to even more
data loss in this case so it should be ok to handle errors where the structure
is correct but cells are corrupted.
> handle corrupted cells like other corrupted WAL cases
> -----------------------------------------------------
>
> Key: HBASE-21817
> URL: https://issues.apache.org/jira/browse/HBASE-21817
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Critical
> Attachments: HBASE-21817.01.patch, HBASE-21817.02.patch,
> HBASE-21817.patch
>
>
> See HBASE-21601 for context.
> I looked at the code a bit but it will take a while to understand, so for now
> I'm going to mitigate it by handling such cases like any other corrupted WAL
> (via either skipErrors or CorruptedHLog exception)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
