You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Koelli Mungee (JIRA)" <ji...@apache.org> on 2018/05/11 04:32:00 UTC
[jira] [Updated] (KAFKA-6897) Mirrormaker waits to shut down
forever on produce failure with abort.on.send.failure=true
[ https://issues.apache.org/jira/browse/KAFKA-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koelli Mungee updated KAFKA-6897:
---------------------------------
Description:
Mirrormaker never shuts down after a produce failure when abort.on.send.failure=true
{code:java}
[2018-05-07 08:29:32,417] ERROR Error when sending message to topic test with key: 52 bytes, value: 32615 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for test-11: 45646 ms has passed since last append
[2018-05-07 08:29:32,434] INFO Closing producer due to send failure. (kafka.tools.MirrorMaker$)
[2018-05-07 08:29:32,434] INFO [Producer clientId=producer-1] Closing the Kafka producer with timeoutMillis = 0 ms. (org.apache.kafka.clients.producer.KafkaProducer)
{code}
A stack trace of this mirrormaker process 9 hours later shows that the main thread is still active and it is waiting for metadata that it will never get since the producer send thread is no longer running.
was:
Mirrormaker never shuts down after a produce failure:
{code:java}
[2018-05-07 08:29:32,417] ERROR Error when sending message to topic test with key: 52 bytes, value: 32615 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for test-11: 45646 ms has passed since last append
[2018-05-07 08:29:32,434] INFO Closing producer due to send failure. (kafka.tools.MirrorMaker$)
[2018-05-07 08:29:32,434] INFO [Producer clientId=producer-1] Closing the Kafka producer with timeoutMillis = 0 ms. (org.apache.kafka.clients.producer.KafkaProducer)
{code}
A stack trace of this mirrormaker process 9 hours later shows that the main thread is still active and it is waiting for metadata that it will never get since the producer send thread is no longer running.
> Mirrormaker waits to shut down forever on produce failure with abort.on.send.failure=true
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-6897
> URL: https://issues.apache.org/jira/browse/KAFKA-6897
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Koelli Mungee
> Priority: Major
>
> Mirrormaker never shuts down after a produce failure when abort.on.send.failure=true
> {code:java}
> [2018-05-07 08:29:32,417] ERROR Error when sending message to topic test with key: 52 bytes, value: 32615 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
> org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for test-11: 45646 ms has passed since last append
> [2018-05-07 08:29:32,434] INFO Closing producer due to send failure. (kafka.tools.MirrorMaker$)
> [2018-05-07 08:29:32,434] INFO [Producer clientId=producer-1] Closing the Kafka producer with timeoutMillis = 0 ms. (org.apache.kafka.clients.producer.KafkaProducer)
> {code}
> A stack trace of this mirrormaker process 9 hours later shows that the main thread is still active and it is waiting for metadata that it will never get since the producer send thread is no longer running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)