As we expected, the new consumer setting `buffer.memory` appears more useful when - there is a need to constrain the overall memory usage of the consumer process and - the consumer subscription is spread among many brokers and - the consumer is configured with a relatively large per-broker `fetch.max.bytes`
[ Full content available at: https://github.com/apache/kafka/pull/4934 ] This message was relayed via gitbox.apache.org for [email protected]
