On 08.12.2017 10:43, Ismael Juma wrote:
One correction below.
On Fri, Dec 8, 2017 at 11:16 AM, Jan Filipiak <jan.filip...@trivago.com>
wrote:
We only check max.message.bytes to late to guard against consumer stalling.
we dont have a notion of max.networkpacket.size before we allocate the
bytebuffer to read it into.
We do: socket.request.max.bytes.
Ismael
perfect, didn't knew we have this in the meantime. :) good that we have it.
Its a very good safeguard. and a nice fail fast for dodgy clients or
network interfaces.
