You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sönke Liebau (Jira)" <ji...@apache.org> on 2020/08/20 15:50:00 UTC
[jira] [Resolved] (KAFKA-9852) Lower block duration in
BufferPoolTest to cut down on overall test runtime
[ https://issues.apache.org/jira/browse/KAFKA-9852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sönke Liebau resolved KAFKA-9852.
---------------------------------
Fix Version/s: 2.6.0
Resolution: Fixed
> Lower block duration in BufferPoolTest to cut down on overall test runtime
> --------------------------------------------------------------------------
>
> Key: KAFKA-9852
> URL: https://issues.apache.org/jira/browse/KAFKA-9852
> Project: Kafka
> Issue Type: Improvement
> Components: unit tests
> Reporter: Sönke Liebau
> Assignee: Sönke Liebau
> Priority: Trivial
> Fix For: 2.6.0
>
>
> In BufferPoolTest we use a global setting for the maximum duration that calls can block (max.block.ms) of [2000ms |https://github.com/apache/kafka/blob/e032a360708cec2284f714e4cae388066064d61c/clients/src/test/java/org/apache/kafka/clients/producer/internals/BufferPoolTest.java#L54]
> Since this is wall clock time that might be waited on and could potentially come into play multiple times while this class is executed this is a very long timeout for testing.
> We should reduce this timeout to a much lower value to cut back on test runtimes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)