The latest articles on DEV Community by Nagarajan Selvaraj (@nagarajan). https://dev.to/nagarajan https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F232817%2Fd6fed0b3-db0f-4201-9d50-9b932f6ef0dc.jpg https://dev.to/nagarajan en Nagarajan Selvaraj Mon, 23 Sep 2019 16:55:42 +0000 https://dev.to/nagarajan/kafka-producer-retries-in-spring-kafka-49fl https://dev.to/nagarajan/kafka-producer-retries-in-spring-kafka-49fl <p>The KafkaProducer configuration has a option(<em>retries</em> property) for doing automatic retries in case of RetriableExceptions like NoLeaderForPartition, NetworkException, TimeoutException etc.</p> <p>The <strong>retries</strong> property has the default value as <strong>Integer.MAX</strong> as per <em><a href="https://kafka.apache.org/documentation/#producerconfigs">https://kafka.apache.org/documentation/#producerconfigs</a></em>. </p> <p>I was using <em>spring-kafka 2.2.8-RELEASE</em> in the application and tried to test the retry behavior by bringing one of the broker down from the Kafka cluster. It thrown the NoLeaderForPartition exception as the leader broker for a partition went down and it took 1-2 seconds for a new leader to be assigned to that partition.</p> <p>As per the documentation, the producer should’ve retried on this exception, but to the surprise it didn’t happen. Digging further, found out that the spring-kafka 2.2.8-RELEASE (Aug 2019, latest in central repo) is using 2.0.1 version of <em>kafka-clients</em> library whereas the kafka-clients library’s latest version is 2.3.0. In kafka-clients 2.0.1 version, the default value for retries is 0.</p> <p>Learning I take away from this is that the <em>latest spring library version need not be using the latest version</em> of the actual client library. Also we need to understand from which version of the client library, the documentation applies to.</p> kafka spring java