[jira] [Updated] (CAMEL-10213) Camel Kafka doesn't support setting "max.poll.records" and "session.timeout.ms"

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-10213:
--------------------------------
    Issue Type: Improvement  (was: Bug)

> Camel Kafka doesn't support setting "max.poll.records" and "session.timeout.ms" 
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-10213
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10213
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-kafka
>    Affects Versions: 2.18.0
>            Reporter: Oliver Holzmann
>            Priority: Critical
>             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 {{session.timeout.ms}} . 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 
> session.timeout.ms, 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 {{session.timeout.ms}} to Kafka endpoint configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)