kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Holford (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-6947) Mirrormaker Closing producer due to send failure
Date Fri, 25 May 2018 07:53:00 GMT
Andrew Holford created KAFKA-6947:

             Summary: Mirrormaker Closing producer due to send failure
                 Key: KAFKA-6947
                 URL: https://issues.apache.org/jira/browse/KAFKA-6947
             Project: Kafka
          Issue Type: Bug
    Affects Versions:
            Reporter: Andrew Holford


On occasion our mirrormakers fail with the below error....

[2018-05-25 05:10:31,695] ERROR Error when sending message to topic com_snapshot--demo with
key: 13 bytes, value: 355 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)

org.apache.kafka.common.errors.TimeoutException: Expiring 38 record(s) for com_snapshot--demo-5:
91886 ms has passed since last append

[2018-05-25 05:10:31,710] INFO Closing producer due to send failure. (kafka.tools.MirrorMaker$)

[2018-05-25 05:10:31,710] INFO Closing the Kafka producer with timeoutMillis = 0 ms. (org.apache.kafka.clients.producer.KafkaProducer)

[2018-05-25 05:10:31,710] INFO Proceeding to force close the producer since pending requests
could not be completed within timeout 0 ms. (org.apache.kafka.clients.producer.KafkaProducer)


On the broker side we see:

WARN Attempting to send response via channel for which there is no open connection, connection
id (kafka.network.Processor)

Does anyone know what could cause this and what a possible solution could be?

Im a little confused by the "timeoutMillis = 0 ms" as well mentioned, is this some setting
which needs adjusting somewhere? We have request.timeout.ms=60000 on the producer config with
most other settings left as the defaults. 

This message was sent by Atlassian JIRA

View raw message