I hate going back and forth on this, but KafkaProducer.close() (with no timeout) is equivalent to close(Long.MAX_VALUE, TimeUnit.MILLISECONDS), while the KafkaConsumer.close() is equivalent to close(30*1000,TimeUnit.MILLISECONDS).
Isn't this kind of inconsistency best to avoid? On Thu, Jan 5, 2017 at 2:08 PM, Rajini Sivaram <rajinisiva...@gmail.com> wrote: > Thank you, Ismael. I have sent another one. Hopefully that will appear in > its own thread. > > Rajini > > On Thu, Jan 5, 2017 at 9:30 PM, Ismael Juma <ism...@juma.me.uk> wrote: > >> Thanks Rajini. This seems to be happening a lot lately: Gmail is showing >> the vote message in the discuss thread. >> >> Ismael >> >> On Thu, Jan 5, 2017 at 9:23 PM, Rajini Sivaram <rajinisiva...@gmail.com> >> wrote: >> >> > Hi all, >> > >> > I would like to start the voting process for *KIP-102 - Add close with >> > timeout for consumers:* >> > >> > https://cwiki.apache.org/confluence/display/KAFKA/KIP- >> > 102+-+Add+close+with+timeout+for+consumers >> > >> > >> > This KIP adds a new close method with a timeout for consumers similar to >> > the close method in the producer. As described in the discussion thread >> > <http://mail-archives.apache.org/mod_mbox/kafka-dev/201612.mbox/%3cCAG_+ >> > n9us5ohthwmyai9pz4s2j62fmils2ufj8oie9jpmyaf...@mail.gmail.com%3e>, >> > the changes are only in the close code path and hence the impact is not >> too >> > big. The existing close() method without a timeout will use a default >> > timeout of 30 seconds. >> > >> > Thank you... >> > >> > Regards, >> > >> > Rajini >> > >> -- Gwen Shapira Product Manager | Confluent 650.450.2760 | @gwenshap Follow us: Twitter | blog
