GitHub user nepal opened a pull request:
https://github.com/apache/kafka/pull/1683
KAFKA-2063: Add possibility to bound fetch response size
Details are:
1. Protocol is extended with new version of FetchRequest with extra
parameter limit_bytes.
2. New config setting fetch.limit.bytes is added. It is set to zero by
default (which means "no limit"), so we preserve old behaviour by default
3. When broker receives FetchRequest with limit_bytes != 0, it performs
random shuffle of partitions before reading is started. This way we can ensure
that no starvation can happen for "slow" partitions
4. For each partition we read up to max_bytes requested for this partition,
even if current value of limit_bytes is greater than zero but less than
max_bytes. This way we can properly handle case when next message in given
partition is larger than current value of limit_bytes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nepal/kafka fetch-request-add-limit
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1683.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1683
----
commit 4f703539bcd46058d036bafd300b98a93dec26a5
Author: Andrey L. Neporada <anepor...@yandex-team.ru>
Date: 2016-07-29T12:28:07Z
KAFKA-2063: Add possibility to bound fetch response size
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
