[
https://issues.apache.org/jira/browse/KAFKA-16197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Rao updated KAFKA-16197:
--
Description:
When a Connect worker's poll timeout expires in Connect, the log lines that we
see are:
{noformat}
consumer poll timeout has expired. This means the time between subsequent calls
to poll() was longer than the configured max.poll.interval.ms, which typically
implies that the poll loop is spending too much time processing messages. You
can address this either by increasing max.poll.interval.ms or by reducing the
maximum size of batches returned in poll() with max.poll.records.
{noformat}
and the reason for leaving the group is
{noformat}
Member XX sending LeaveGroup request to coordinator XX due to consumer poll
timeout has expired.
{noformat}
which is specific to Consumers and not to Connect workers. The log line above
in specially misleading because the config `max.poll.interval.ms` is not
configurable for a Connect worker and could make someone believe that the logs
are being written for Sink Connectors and not for Connect worker. Ideally, we
should print something specific to Connect.
was:
When a worker's poll timeout expires in Connect, the log lines that we see are:
{noformat}
consumer poll timeout has expired. This means the time between subsequent calls
to poll() was longer than the configured max.poll.interval.ms, which typically
implies that the poll loop is spending too much time processing messages. You
can address this either by increasing max.poll.interval.ms or by reducing the
maximum size of batches returned in poll() with max.poll.records.
{noformat}
and the reason for leaving the group is
{noformat}
Member XX sending LeaveGroup request to coordinator XX due to consumer poll
timeout has expired.
{noformat}
which is specific to Consumers and not to Connect workers. The log line above
in specially misleading because the config `max.poll.interval.ms` is not
configurable for a Connect worker and could make someone believe that the logs
are being written for Sink Connectors and not for Connect worker. Ideally, we
should print something specific to Connect.
> Connect Worker poll timeout prints Consumer poll timeout specific warnings.
> ---
>
> Key: KAFKA-16197
> URL: https://issues.apache.org/jira/browse/KAFKA-16197
> Project: Kafka
> Issue Type: Bug
> Components: connect
>Reporter: Sagar Rao
>Assignee: Sagar Rao
>Priority: Major
>
> When a Connect worker's poll timeout expires in Connect, the log lines that
> we see are:
> {noformat}
> consumer poll timeout has expired. This means the time between subsequent
> calls to poll() was longer than the configured max.poll.interval.ms, which
> typically implies that the poll loop is spending too much time processing
> messages. You can address this either by increasing max.poll.interval.ms or
> by reducing the maximum size of batches returned in poll() with
> max.poll.records.
> {noformat}
> and the reason for leaving the group is
> {noformat}
> Member XX sending LeaveGroup request to coordinator XX due to consumer poll
> timeout has expired.
> {noformat}
> which is specific to Consumers and not to Connect workers. The log line above
> in specially misleading because the config `max.poll.interval.ms` is not
> configurable for a Connect worker and could make someone believe that the
> logs are being written for Sink Connectors and not for Connect worker.
> Ideally, we should print something specific to Connect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
