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.
