[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488682#comment-15488682
]
Vahid Hashemian edited comment on KAFKA-4126 at 9/13/16 10:43 PM:
------------------------------------------------------------------
[~balazs.barnabas] [~omkreddy] When I try this use case with the console
producer with the trunk code-base. This is what I observe after entering the
first message into a non-existing topic {{new_topic}}:
* On the client side, I see this warning: {{[2016-09-13 15:34:29,259] WARN
Error while fetching metadata with correlation id 0 :
\{new_topic=LEADER_NOT_AVAILABLE\} (org.apache.kafka.clients.NetworkClient)}}
* On the server side, I see this message among some other {{INFO}} level logs:
{{[2016-09-13 15:34:29,238] INFO [KafkaApi-0] Auto creation of topic new_topic
with 1 partitions and replication factor 1 is successful
(kafka.server.KafkaApis)}}
I don't see the [~omkreddy]'s warning above, and see the {{INFO}} level log on
the server side that indicates the topic did not exist but auto-created. Can
you clarify the use case, and the requirement? Thanks.
was (Author: vahid):
[~balazs.barnabas] [~omkreddy] When I try this use case with the console
producer with the trunk code-base. This is what I observe after entering the
first message into a non-existing topic {{new_topic}}:
* On the client side, I see this warning: {{[2016-09-13 15:34:29,259] WARN
Error while fetching metadata with correlation id 0 :
{new_topic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)}}
* On the server side, I see this message among some other {{INFO}} level logs:
{{[2016-09-13 15:34:29,238] INFO [KafkaApi-0] Auto creation of topic new_topic
with 1 partitions and replication factor 1 is successful
(kafka.server.KafkaApis)}}
I don't see the [~omkreddy]'s warning above, and see the {{INFO}} level log on
the server side that indicates the topic did not exist but auto-created. Can
you clarify the use case, and the requirement? Thanks.
> No relevant log when the topic is non-existent
> ----------------------------------------------
>
> Key: KAFKA-4126
> URL: https://issues.apache.org/jira/browse/KAFKA-4126
> Project: Kafka
> Issue Type: Bug
> Reporter: Balázs Barnabás
> Assignee: Vahid Hashemian
> Priority: Minor
>
> When a producer sends a ProducerRecord into a Kafka topic that doesn't
> existst, there is no relevant debug/error log that points out the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
