[
https://issues.apache.org/jira/browse/HDDS-16081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101559#comment-18101559
]
Sergey Soldatov commented on HDDS-16081:
----------------------------------------
Here is the failure.
{noformat}
2026-08-03T23:53:49.4486237Z [ERROR]
org.apache.hadoop.ozone.om.TestOMRatisSnapshots.testInstallSnapshotWithClientWrite
-- Time elapsed: 33.76 s <<< FAILURE!
2026-08-03T23:53:49.4488431Z org.opentest4j.AssertionFailedError: expected: not
<null>
2026-08-03T23:53:49.4489756Z at
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
2026-08-03T23:53:49.4490942Z at
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
2026-08-03T23:53:49.4491873Z at
org.junit.jupiter.api.AssertNotNull.failNull(AssertNotNull.java:49)
2026-08-03T23:53:49.4492697Z at
org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:35)
2026-08-03T23:53:49.4493557Z at
org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:30)
2026-08-03T23:53:49.4494267Z at
org.junit.jupiter.api.Assertions.assertNotNull(Assertions.java:304)
2026-08-03T23:53:49.4494843Z at
org.apache.hadoop.ozone.om.TestOMRatisSnapshots.testInstallSnapshotWithClientWrite(TestOMRatisSnapshots.java:336)
2026-08-03T23:53:49.4495378Z at
java.base/java.lang.reflect.Method.invoke(Method.java:565)
2026-08-03T23:53:49.4495770Z at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:511)
2026-08-03T23:53:49.4496534Z at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1450)
2026-08-03T23:53:49.4497290Z at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:2019)
2026-08-03T23:53:49.4498271Z at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)
{noformat}
> Flaky TestOMRatisSnapshots#testInstallSnapshotWithClientWrite: follower may
> not have all keys when the leader's last applied index is reached
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-16081
> URL: https://issues.apache.org/jira/browse/HDDS-16081
> Project: Apache Ozone
> Issue Type: Test
> Components: Snapshot, test
> Affects Versions: 2.3.0
> Reporter: Sergey Soldatov
> Assignee: Sergey Soldatov
> Priority: Minor
>
> testInstallSnapshotWithClientWrite fails intermittently with "expected: not
> <null>" when it verifies that the follower OM's DB contains the keys written
> after the follower was started. The test waits for the follower's last
> applied index to reach the leader's and reads the keys directly from the
> follower's DB. An OM acks a write as soon as the response is added to the
> double buffer, but the last applied index only advances *after* the double
> buffer commits the batch to RocksDB. When the client writes return, the
> leader's applied index can still be behind the last key written, and the
> follower.
> This appears after HDDS-10310, which replaced the Thread.sleep(5000) with
> the index-based wait, and removed the per-key sleep from the write loop,
> making the writes fast enough to widen the window.
> [~chihsuan] Please let me know if my RCA was wrong.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
