You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Ramkishan (Jira)" <ji...@apache.org> on 2019/09/16 20:47:00 UTC

[jira] [Updated] (KAFKA-8912) TimeoutException cause is insufficiently documented for the KafkProducer

     [ https://issues.apache.org/jira/browse/KAFKA-8912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramkishan updated KAFKA-8912:
-----------------------------
    Summary: TimeoutException cause is insufficiently documented for the KafkProducer  (was: TimeoutException cause is insufficiently articulated for the KafkProducer)

> TimeoutException cause is insufficiently documented for the KafkProducer
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-8912
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8912
>             Project: Kafka
>          Issue Type: Bug
>          Components: documentation, producer 
>    Affects Versions: 0.10.0.1, 2.2.1
>            Reporter: Ramkishan
>            Priority: Major
>
> The javadocs of the org.apache.kafka.clients.producer.KafkaProducer class has partially articulated description for the TimeoutException, wherever applicable.
> The document reads - "{{[TimeoutException|https://kafka.apache.org/23/javadoc/org/apache/kafka/common/errors/TimeoutException.html]}} - If the time taken for fetching metadata or allocating memory for the record has surpassed {{max.block.ms}}."
> While we are aware that this exception can also be thrown if the RTM occurs when the message is on the accumulator and the batch expires. The current description is misleading the developers who try to optimize the producer config and if they face this issue
> [https://kafka.apache.org/23/javadoc/org/apache/kafka/common/errors/TimeoutException.html]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)