apupier opened a new pull request, #29177: URL: https://github.com/apache/camel/pull/29177
# Description [CAMEL-26593](https://issues.apache.org/jira/browse/CAMEL-26593): since CAMEL-24781 (5b6ee1efaaad) the Kafka exactly-once ITs are on the critical path of the build and take several minutes. This is a first iteration that removes waiting time that cannot change the outcome of the tests. - `KafkaExactlyOnceIT#sedaIsTheOnlyPathToKafka` and `#splitFanOutToKafka` took ~31s each, versus ~2s for the other tests of the class. Both routes are rejected by the exactly-once claim check (`ClaimRejectedException`), so the source record is replayed in a loop and the offset is never committed, but the tests still waited the full 30s timeout for a commit. They now stop waiting as soon as the record has been replayed (new `awaitCommittedOrReplayed` in `KafkaExactlyOnceITSupport`). Assertions are unchanged. - `KafkaExactlyOnceRegressionIT#readCommitted` assigns the partitions directly instead of joining a consumer group, waits for the topic to exist, and uses a shorter quiet period (1.5s) to detect late duplicates or unexpected records. The assertion on the exact number of committed records is unchanged. Local timings (one Kafka container per class, `serials-test` execution): | Class | Before | After | |---|---|---| | `KafkaExactlyOnceIT` | 120.2 s | 49.0 s | | `KafkaExactlyOnceRebalanceIT` | 9.2 s | 8.0 s | | `KafkaExactlyOnceRegressionIT` | 78.5 s | 71.3 s | All 55 tests pass before and after. Not addressed here: `KafkaExactlyOnceRegressionIT` is made of 23 tests of 2-8s each, mostly Kafka topic/consumer/transactional-producer start-up and deliberate "nothing happened" checks. The `serials-test` execution also uses `reuseForks=false`, so each class starts its own JVM and Kafka container. Both could be follow-ups. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. --- _IBM Bob 2.2.1 on behalf of apupier_ -- 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]
