The examples in the javadoc seems to imply that developers need to manage all of the aspects around failures. Those examples are for rewinding offsets, dealing with failed portioned for instance.
On Thu, Oct 22, 2015 at 11:17 AM, Guozhang Wang <wangg...@gmail.com> wrote: > Hi Mohit: > > In general new consumers will abstract developers from any network > failures. More specifically. > > 1) consumers will automatically try to re-fetch the messages if the > previous fetch has failed. > 2) consumers will remember the currently fetch positions after each > successful fetch, and can periodically commit these offsets back to Kafka. > > Guozhang > > On Thu, Oct 22, 2015 at 10:11 AM, Mohit Anchlia <mohitanch...@gmail.com> > wrote: > > > It looks like the new consumer API expects developers to manage the > > failures? Or is there some other API that can abstract the failures, > > primarily: > > > > 1) Automatically resent failed messages because of network issue or some > > other issue between the broker and the consumer > > 2) Ability to acknowledge receipt of a message by the consumer such that > > message is sent again if consumer fails to acknowledge the receipt. > > > > Is there such an API or are the clients expected to deal with failure > > scenarios? > > > > Docs I am looking at are here: > > > > http://people.apache.org/~nehanarkhede/kafka-0.9-consumer-javadoc/doc/ > > > > > > -- > -- Guozhang >
