[
https://issues.apache.org/jira/browse/HBASE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077312#comment-14077312
]
Andrew Purtell commented on HBASE-11595:
----------------------------------------
Further discussion on dev@ revealed the reporter changed the WAL reader class
in the site configuration back to default between crash and restart. Therefore,
the encrypted WAL could not be read. There might still be an issue here with a
"corrupt" WAL being improperly moved to oldWALs/ but let's follow up on another
issue. Resolving as invalid.
> WAL files with encryption not flushed properly
> ----------------------------------------------
>
> Key: HBASE-11595
> URL: https://issues.apache.org/jira/browse/HBASE-11595
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.3
> Reporter: Andrew Purtell
> Priority: Critical
>
> Reported using HBase 0.98.3 and HDFS 2.4.1
> All data before failure has not yet been flushed so only exists in the WAL
> files. During distributed splitting, the WAL has either not been written out
> and synced in the same way as an unencrypted WAL or is unreadable:
> {noformat}
> 2014-07-26 19:29:16,160 ERROR [RS_LOG_REPLAY_OPS-host1:60020-0]
> codec.BaseDecoder: Partial cell read caused by EOF: java.io.IOException:
> Premature EOF from inputStream
> {noformat}
> This file is still moved to oldWALs even though splitting failed.
> Setting 'hbase.regionserver.wal.encryption' to false allows data recovery.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
