camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10213) Camel Kafka doesn't support setting "max.poll.records" and ""
Date Fri, 18 Nov 2016 17:44:59 GMT


ASF GitHub Bot commented on CAMEL-10213:

GitHub user landonvg opened a pull request:

    Fix docs for maxPollRecords

    This syncs up the default and description with max.poll.records;
see comment in

You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1279
commit fda945f64ea71cb4589599e850edf20cb98abbaa
Author: Von Landon <>
Date:   2016-11-18T17:41:03Z

    Fix docs for maxPollRecords
    This syncs up the default and description with max.poll.records
; see comment in

commit 5eced81a83ece9407bb86c8358be4ca9b33e1288
Author: Von Landon <>
Date:   2016-11-18T17:41:53Z

    Merge pull request #1 from landonvg/landonvg-patch-1
    Fix docs for maxPollRecords


> Camel Kafka doesn't support setting "max.poll.records" and "" 
> --------------------------------------------------------------------------------
>                 Key: CAMEL-10213
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-kafka
>    Affects Versions: 2.18.0
>            Reporter: Oliver Holzmann
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.18.0
> Currently it is not possible to control the processing time in the poll loop in Camel
Kafka consumers. 
> It is important to have the possibility to control the poll loop by adjusting {{max.poll.records}}
and {{}} . Otherwise this warning is produced when consuming a large backlog
from kafka topic:
> {code}
> Auto offset commit failed for group consumerGroup: Commit cannot be 
> completed since the group has already rebalanced and assigned the 
> partitions to another member. This means that the time between 
> subsequent calls to poll() was longer than the configured 
>, which typically implies that the poll loop is spending 
> too much time message processing. You can address this either by 
> increasing the session timeout or by reducing the maximum size of batches
> returned in poll() with max.poll.records.
> {code}
> Please add {{max.poll.records}} and {{}} to Kafka endpoint configuration.

This message was sent by Atlassian JIRA

View raw message