Joshua Scott

Is this fixed now? we raise a specific error for this case (changed in #268) https://github.com/kafkaex/kafka_ex/blob/b0d472b2919e40ba403ad1e3b3a9224290827788/lib/kafka_ex/protocol/fetch.ex#L77 not sure what else we could do to handle the issue.

it appears as though the message size is 825MB, which means you need to increase max_bytes to at least that size to be able to consume it. As an aside,...

The answer at this point is to ensure your max_bytes matches the topic's max_bytes. We treat max_bytes as a requirement in kafka_ex, so if it is lower than the topic's...

I haven't observed this in a while - I believe the heartbeating is now catching this and refreshing the metadata if a broker is actually down (not just temporarily unreachable)....

I rechecked a repo and indeed this problem has been solved at some point. I'm running: ``` Erlang/OTP 25 [erts-13.1.3] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns] Elixir 1.14.2 (compiled with...

> @joshuawscott thanks ! Do we need a tag or something for this to happen ? Are you sure it's automatic ? @jbruggem It's not automatic, but tagging does happen...