PatrickPeng

@AmiKotia I also encountered a similar problem. The reasons for the problem were mentioned in the comments of this question.https://github.com/IBM/sarama/issues/2682

 I captured packets from kafka in the test environment and found that no fetch_reqeust was initiated for the abnormal topic origdata_log_http, but fetch_request was sent to other topics.

I think I have found the cause of the problem. I read the source code of sarama. When multiple shards of a topic return ErrOutofRange, the brokerConumer.subscriptions will eventually become...

   I think sarama should handle this OutOfRangeError, because for users, they don't know how to handle this error, but the final result is that consumers stop consuming....

@phallstrom