Hi Ismael, Treating commitSync as heartbeat will definitely resolve the issue i am facing but the reason behind my issue does not seem to be what mentioned in defect (i.e frequent commitSync requests).
I am sending CommitSync periodically only to keep my session alive when my consumer is still processing records and is close to session time out (tried 10th / 12th / 15th / 20th second after poll called where session time is 30). I see heartbeat response received in logs along with each commitSync call but this stops after a meta data refresh request is issued. I see in logs that commit goes successful but no heartbeat response received message in logs after meta refresh till next poll. Regards, Vinay Sharma On Mon, Apr 25, 2016 at 5:06 PM, Ismael Juma <ism...@juma.me.uk> wrote: > Hi Vinay, > > This was fixed via https://issues.apache.org/jira/browse/KAFKA-3470 (will > be part of 0.10.0.0). > > Ismael > > > > On Mon, Apr 25, 2016 at 1:52 PM, vinay sharma <vinsharma.t...@gmail.com> > wrote: > > > Hello, > > > > I am using client API 0.9.0.1 and facing an issue. As per my logs it > seems > > that on each commitSync(Offsets) a heartbeat request is sent but after a > > metada refresh request till next poll(), commits do not send any hearbeat > > request. > > > > KafkaConsumers i create sometimes get session time out due to no hearbeat > > specially during longer processing times. I call CommitSync(offsets) > after > > regular intervals to keep session alive when processing takes longer than > > usual. Every thing works fine if commit intervals are very small or if i > > commit after each record but if i commit lets say every 12 seconds and 30 > > seconds is session time then i can see consumer getting timed out > > sometimes. > > > > Any help or pointers will be much appreciated. Thanks in advance. > > > > Regards, > > Vinay sharma > > >
