[ https://issues.apache.org/jira/browse/KAFKA-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730421#comment-16730421 ]
Bob Barrett commented on KAFKA-6833: ------------------------------------ Thanks for the suggestion, [~ChrisEgerton]! I agree with [~mageshn], I think that's a better approach. > KafkaProducer throws "Invalid partition given with record" exception > -------------------------------------------------------------------- > > Key: KAFKA-6833 > URL: https://issues.apache.org/jira/browse/KAFKA-6833 > Project: Kafka > Issue Type: Bug > Affects Versions: 1.0.0 > Reporter: Arjun Satish > Assignee: Bob Barrett > Priority: Minor > > Currently, when creating topics via ZooKeeper, there is a small but definite > delay between creating the nodes in ZK, and having the topics created in the > brokers. the KafkaProducer maintains a metadata cache about topics which get > updated after the broker metadata is updated. If an application adds > partitions to a topic, and immediately tries to produce records to a new > partition, a KafkaException is throw with a message similar to the following: > {code:java} > Caused by: org.apache.kafka.common.KafkaException: Invalid partition given > with record: 12 is not in the range [0...1). > {code} > In this case, since the application has context that it created the topics, > it might be worthwhile to consider if a more specific exception can be thrown > instead of KafkaException. For example: > {code:java} > public class PartitionNotFoundException extends KafkaException {...}{code} > This could allow the application to be able to interpret such an error, and > act accordingly. > EDIT: Correct "create topics" to "adds partitions to a topic". -- This message was sent by Atlassian JIRA (v7.6.3#76005)