Jackie-Jiang opened a new issue, #20095: URL: https://github.com/apache/pinot/issues/20095
`TableRebalanceIntegrationTest.testForceCommit[0]` intermittently fails when the force-commit/rebalance test expects consuming segment sequence 12 but observes 13. ### Failed CI runs Both failures are in **Pinot Integration Test Set 2 (temurin-25), lane B**: - [PR #20087, run 40863677182, job 123412934902](https://github.com/apache/pinot/actions/runs/40863677182/job/123412934902), head `b2cb8cc1d8cd6ce19a616f6afe5e2a26206504a0`. - [Master, run 40281981998, job 121437084642](https://github.com/apache/pinot/actions/runs/40281981998/job/121437084642), commit `c5b8107fa6a0e0bcf7f1b401cc2aa827a7e32e74`. The master failure has the same assertion and stack and used dnsjava 3.6.5. It therefore predates #20087's dnsjava bump. [Integration Set 2 on the PR's base commit passed](https://github.com/apache/pinot/actions/runs/40855315164/job/123384691768). ### Failure ```text java.lang.AssertionError: expected [12] but found [13] at BaseClusterIntegrationTestSet.performForceCommitSegmentMovingTest(BaseClusterIntegrationTestSet.java:1164) at BaseClusterIntegrationTestSet.performForceCommitSegmentMovingTest(BaseClusterIntegrationTestSet.java:1098) at TableRebalanceIntegrationTest.testForceCommit(TableRebalanceIntegrationTest.java:1287) ``` This was the only failure among the PR job's lane B tests (362 tests). [The assertion](https://github.com/apache/pinot/blob/b2cb8cc1d8cd6ce19a616f6afe5e2a26206504a0/pinot-integration-tests/src/test/java/org/apache/pinot/integration/tests/BaseClusterIntegrationTestSet.java#L1154-L1166) expects the consuming segment sequence number after rebalance to equal the original sequence number plus one. The observed value is one higher than that expectation. [The failing invocation](https://github.com/apache/pinot/blob/b2cb8cc1d8cd6ce19a616f6afe5e2a26206504a0/pinot-integration-tests/src/test/java/org/apache/pinot/integration/tests/TableRebalanceIntegrationTest.java#L1283-L1288) is the first tenant move under strict replica group routing. ### Investigation direction The existing console logs do not establish whether there was an additional segment rollover/commit or an asynchronous observation race. Capture the original and current consuming segment identities per partition, their sequence numbers, and the commit reasons around the rebalance to identify the cause and make the test deterministic. Diagnosis is based on CI logs and source inspection; no local reproduction has been run. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
