You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2025/03/12 10:48:00 UTC

[jira] [Created] (HBASE-29183) Fix flakeyness on TestVerifyBucketCacheFile

Wellington Chevreuil created HBASE-29183:
--------------------------------------------

             Summary: Fix flakeyness on TestVerifyBucketCacheFile
                 Key: HBASE-29183
                 URL: https://issues.apache.org/jira/browse/HBASE-29183
             Project: HBase
          Issue Type: Bug
            Reporter: Wellington Chevreuil
            Assignee: Wellington Chevreuil


I've noticed some flakeyness in some of the tests from TestVerifyBucketCacheFile. One of the latest intermittent failures I've found on the precommit run for a PR:
{noformat}
java.lang.AssertionError: expected:<0> but was:<17408>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:633)
	at org.apache.hadoop.hbase.io.hfile.bucket.TestVerifyBucketCacheFile.testModifiedBucketCacheFileData(TestVerifyBucketCacheFile.java:247) {noformat}
These are quite hard to reproduce locally, but after analysing the test code and the stack trace, I believe this might be related to the changes from HBASE-28900, which allowed BucketAllocator to complete initialisation with a partially recovered cache, requiring the backingMap validation to complete, in order to get rid of entries with inconsistent checksums.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)