mirror of https://github.com/apache/kafka.git
[As discussed in the mailing list](https://lists.apache.org/thread/m03mpkm93737kk6d1nd6fbv9wdgsrhv9), the broker only fetches remote data for ONE partition in a given FetchRequest. In other words, if a consumer sends a FetchRequest requesting 50 topic-partitions, and each partition's requested offset is not stored locally - the broker will fetch and respond with just one partition's worth of data from the remote store, and the rest will be empty. Given our defaults for total fetch response is 50 MiB and per partition is 1 MiB, this can limit throughput. This patch documents the behavior in 3 configs - `fetch.max.bytes`, `max.partition.fetch.bytes` and `remote.fetch.max.wait.ms` Reviewers: Luke Chen <showuon@gmail.com>, Kamal Chandraprakash <kamal.chandraprakash@gmail.com>, Satish Duggana <satishd@apache.org> |
||
---|---|---|
.. | ||
api/src | ||
src |