1

I am using spring kafka to implement kafka listener with default properties. I have noticed that with some failure eg: broker not available or any internal call failure after consuming message, it stops consuming messages and I can see attached error while commiting previous consumed message.

How can we make our kafka consumer to reconnect to group and start consuming message without pod restart in kubernetes? As currently when we restart our kubernetes pod the kafka consumer starts listening to message from last committed offset.

screenshot showing error message

jagmohansharma
  • 61
  • 1
  • 6
  • what is your settings for reconnect.backoff.ms ? – Roger Alkins Sep 21 '20 at 04:34
  • I am not overriding these properties for reconnect. It is used as default. But here I'm asking for reconnection possibilities after consumer is out of active group which stops it to consume message. – jagmohansharma Sep 22 '20 at 12:19

0 Answers0