[KAFKA-16372] max.block.ms behavior inconsistency with javadoc and the config description

• Type: Bug
• Status: In Progress
• Priority: Minor
• Resolution: Unresolved
• Component/s: producer
• Assignee: Haruki Okada
• Reporter: Haruki Okada
• Created: 14/Mar/24 10:25
• Updated: 09/Aug/24 03:10

Description

As of Kafka 3.7.0, the javadoc of KafkaProducer.send states that it throws TimeoutException when max.block.ms is exceeded on buffer allocation or initial metadata fetch.

Also it's stated in buffer.memory config description.

However, I found that this is not true because TimeoutException extends ApiException, and KafkaProducer.doSend catches ApiException and wraps it as FutureFailure instead of throwing it.

I wonder if this is a bug or the documentation error.

Seems this discrepancy exists since 0.9.0.0, which max.block.ms is introduced.

Issue Links

• is duplicated by: KAFKA-16651 KafkaProducer.send does not throw TimeoutException as documented
• links to: GitHub Pull Request #15574