@tambach At consume time what the consumer do is polling on a socket to see if there is new messages. If there no new messages there is a timeout as you pointed out in your last message. You can't make the difference between no new message and kafka stopped responding. So you could increase the timeout, checkout the librdkafka config for the correct one. But if you increase this timeout you also increase the time before rdkafka detect a problem. For my part I totaly ignore thoses errors, I mainly detect issues by measuring lag between produced messages and consumed messages on topic partitions (Not feasable with phprkafka at this time). Sorry for the long response.