Closed JohnRoesler closed 1 year ago
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur. Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.
Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Configuration
What configuration values are you using for Sarama and Kafka?
Logs
Problem Description
While my broker was undergoing maintenance and the leader was being swapped I saw all my consumer applications log this error and then never continue consuming.
Is there a better solution than logging fatally when I receive one of these errors from the consume client to force my application to restart?
Or is there anything in the recent releases that addresses this issue?