[jira] [Updated] (KAFKA-16695) Improve expired poll interval logging by showing exceeded time
[ https://issues.apache.org/jira/browse/KAFKA-16695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans updated KAFKA-16695: --- Fix Version/s: 3.8.0 > Improve expired poll interval logging by showing exceeded time > -- > > Key: KAFKA-16695 > URL: https://issues.apache.org/jira/browse/KAFKA-16695 > Project: Kafka > Issue Type: Task > Components: clients, consumer >Reporter: Lianet Magrans >Assignee: Lianet Magrans >Priority: Major > Labels: kip-848-client-support > Fix For: 3.8.0 > > > When a consumer poll iteration takes longer than the max.poll.interval, the > consumer logs a warn suggesting that the max.poll.interval config was > exceeded, and pro-actively leaves the group. The log suggests to consider > adjusting the max.poll.interval.config which should help in the cases of long > processing times. We should consider adding the info of how much time the > interval was exceeded, since it could be helpful in guiding the user to > effectively adjust the config. This is done in other clients, that log this > kind of messages in this situation: > {quote}Application maximum poll interval (30ms) exceeded by 255ms (adjust > max.poll.interval.ms for long-running message processing): leaving > group{quote} > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-16695) Improve expired poll interval logging by showing exceeded time
[ https://issues.apache.org/jira/browse/KAFKA-16695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans updated KAFKA-16695: --- Labels: kip-848-client-support (was: ) > Improve expired poll interval logging by showing exceeded time > -- > > Key: KAFKA-16695 > URL: https://issues.apache.org/jira/browse/KAFKA-16695 > Project: Kafka > Issue Type: Task > Components: clients, consumer >Reporter: Lianet Magrans >Assignee: Lianet Magrans >Priority: Major > Labels: kip-848-client-support > > When a consumer poll iteration takes longer than the max.poll.interval, the > consumer logs a warn suggesting that the max.poll.interval config was > exceeded, and pro-actively leaves the group. The log suggests to consider > adjusting the max.poll.interval.config which should help in the cases of long > processing times. We should consider adding the info of how much time the > interval was exceeded, since it could be helpful in guiding the user to > effectively adjust the config. This is done in other clients, that log this > kind of messages in this situation: > {quote}Application maximum poll interval (30ms) exceeded by 255ms (adjust > max.poll.interval.ms for long-running message processing): leaving > group{quote} > -- This message was sent by Atlassian Jira (v8.20.10#820010)