Its using the sync producer without waiting for any broker to acknowledge the write. This explains the lack of errors you are seeing.
— Sent from Mailbox On Fri, Oct 17, 2014 at 3:15 PM, Mohit Anchlia <mohitanch...@gmail.com> wrote: > Little confused :) From one of the examples I am using property > request.required.acks=0, > I thought this sets the producer to be async? > On Fri, Oct 17, 2014 at 11:59 AM, Gwen Shapira <gshap...@cloudera.com> > wrote: >> 0.8.1.1 producer is Sync by default, and you can set producer.type to >> async if needed. >> >> On Fri, Oct 17, 2014 at 2:57 PM, Mohit Anchlia <mohitanch...@gmail.com> >> wrote: >> > Thanks! How can I tell if I am using async producer? I thought all the >> > sends are async in nature >> > On Fri, Oct 17, 2014 at 11:44 AM, Gwen Shapira <gshap...@cloudera.com> >> > wrote: >> > >> >> If you have "auto.create.topics.enable" set to "true" (default), >> >> producing to a topic creates it. >> >> >> >> Its a bit tricky because the "send" that creates the topic can fail >> >> with "leader not found" or similar issue. retrying few times will >> >> eventually succeed as the topic gets created and the leader gets >> >> elected. >> >> >> >> Is it possible that you are not getting errors because you are using >> >> async producer? >> >> >> >> Also "no messages are delivered" can have many causes. Check if the >> >> topic exists using: >> >> bin/kafka-topics.sh --list --zookeeper localhost:2181 >> >> >> >> Perhaps the topic was created and the issue is elsewhere (the consumer >> >> is a usual suspect! perhaps look in the FAQ for tips with that issue) >> >> >> >> Gwen >> >> >> >> On Fri, Oct 17, 2014 at 12:56 PM, Mohit Anchlia <mohitanch...@gmail.com >> > >> >> wrote: >> >> > Is Kafka supposed to throw exception if topic doesn't exist? It >> appears >> >> > that there is no exception thrown even though no messages are >> delivered >> >> and >> >> > there are errors logged in Kafka logs. >> >> >>
