edoardocomar commented on code in PR #13291: URL: https://github.com/apache/kafka/pull/13291#discussion_r1117306285
########## connect/runtime/src/test/java/org/apache/kafka/connect/integration/ExactlyOnceSourceIntegrationTest.java: ########## @@ -266,6 +267,7 @@ public void testPollBoundary() throws Exception { props.put(NAME_CONFIG, CONNECTOR_NAME); props.put(TRANSACTION_BOUNDARY_CONFIG, POLL.toString()); props.put(MESSAGES_PER_POLL_CONFIG, Integer.toString(recordsProduced)); + props.put(THROUGHPUT_CONFIG, Integer.toString(recordsProduced)); Review Comment: the config is a Long, so these settings could be Long.toString(100L) I checked the test that OOM'ing for me too and the number of records actually produced with your setting is still much larger than actually erquired. I found using the same variable `recordsProduced` for throughput was a bit puzzling, maybe just using another literal would be ok. ########## connect/runtime/src/test/java/org/apache/kafka/connect/integration/ExactlyOnceSourceIntegrationTest.java: ########## @@ -81,6 +81,7 @@ import static org.apache.kafka.connect.integration.MonitorableSourceConnector.CUSTOM_EXACTLY_ONCE_SUPPORT_CONFIG; import static org.apache.kafka.connect.integration.MonitorableSourceConnector.CUSTOM_TRANSACTION_BOUNDARIES_CONFIG; import static org.apache.kafka.connect.integration.MonitorableSourceConnector.MESSAGES_PER_POLL_CONFIG; +import static org.apache.kafka.connect.integration.MonitorableSourceConnector.THROUGHPUT_CONFIG; Review Comment: this could be THROUGHPUT_MSGS_PER_SEC_CONFIG -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org