[
https://issues.apache.org/jira/browse/HBASE-27073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687968#comment-17687968
]
Duo Zhang commented on HBASE-27073:
-----------------------------------
Ah, I think I found the possible cause of the problem...
I added some breakpoint when we hit exception while reading the broken WAL file
provided by [~Xiaolin Ha], it turned out that, if the value length is 0, then
the compressed length will be 4, but while reading, we will read nothing so we
will not read the 4 bytes, so when we want to move to the next cell, we will
start reading from the wrong position and cause strange problem...
Let me see if I can reproduce this problem with a simpler test case.
Thanks.
> TestReplicationValueCompressedWAL.testMultiplePuts is flaky
> -----------------------------------------------------------
>
> Key: HBASE-27073
> URL: https://issues.apache.org/jira/browse/HBASE-27073
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.5.0
> Environment: Java version: 1.8.0_322
> OS name: "linux", version: "5.10.0-13-arm64", arch: "aarch64", family: "unix"
> Reporter: Andrew Kyle Purtell
> Priority: Minor
> Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.4
>
>
> org.apache.hadoop.hbase.replication.regionserver.TestReplicationValueCompressedWAL.testMultiplePuts
> 
Run 1: TestReplicationValueCompressedWAL.testMultiplePuts:56 Waited too
> much time for replication
> Run 2: PASS
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
