You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/09 21:41:18 UTC
[jira] [Commented] (KAFKA-5422) Multiple produce request failures
causes invalid state transition in TransactionManager
[ https://issues.apache.org/jira/browse/KAFKA-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045069#comment-16045069 ]
ASF GitHub Bot commented on KAFKA-5422:
---------------------------------------
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3285
KAFKA-5422: Handle multiple transitions to ABORTABLE_ERROR correctly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka KAFKA-5422-allow-multiple-transitions-to-abortable-error
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3285.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3285
----
commit a3d0d923a76269d55541294447967167c35baebb
Author: Apurva Mehta <ap...@confluent.io>
Date: 2017-06-09T21:39:49Z
Handle multiple transitions to ABORTABLE_ERROR correctly
----
> Multiple produce request failures causes invalid state transition in TransactionManager
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-5422
> URL: https://issues.apache.org/jira/browse/KAFKA-5422
> Project: Kafka
> Issue Type: Bug
> Reporter: Apurva Mehta
> Assignee: Apurva Mehta
> Labels: exactly-once
> Fix For: 0.11.0.0
>
>
> When multiple produce requests fail (for instance when all inflight batches are expired), each will try to transition to ABORTABLE_ERROR.
> However, only the first transition will succeed, the rest will fail with the following 'invalid transition from ABORTABLE_ERROR to ABORTABLE_ERROR'.
> This will be caught in the sender thread and things will continue. However, the correct thing to do do is to allow multiple transitions to ABORTABLE_ERROR.
> {noformat}
> [2017-06-09 01:22:39,327] WARN Connection to node 3 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
> [2017-06-09 01:22:39,958] TRACE Expired 2 batches in accumulator (org.apache.kafka.clients.producer.internals.Sender)
> [2017-06-09 01:22:39,958] DEBUG [TransactionalId my-first-transactional-id] Transition from state COMMITTING_TRANSACTION to error state ABORTABLE_ERROR (org.apache.kafka.clients.producer.internals.TransactionManager)
> org.apache.kafka.common.errors.TimeoutException: Expiring 250 record(s) for output-topic-0: 30099 ms has passed since batch creation plus linger time
> [2017-06-09 01:22:39,960] TRACE Produced messages to topic-partition output-topic-0 with base offset offset -1 and error: {}. (org.apache.kafka.clients.producer.internals.ProducerBatch)
> org.apache.kafka.common.errors.TimeoutException: Expiring 250 record(s) for output-topic-0: 30099 ms has passed since batch creation plus linger time
> [2017-06-09 01:22:39,960] ERROR Uncaught error in kafka producer I/O thread: (org.apache.kafka.clients.producer.internals.Sender)
> org.apache.kafka.common.KafkaException: Invalid transition attempted from state ABORTABLE_ERROR to state ABORTABLE_ERROR
> at org.apache.kafka.clients.producer.internals.TransactionManager.transitionTo(TransactionManager.java:475)
> at org.apache.kafka.clients.producer.internals.TransactionManager.transitionToAbortableError(TransactionManager.java:288)
> at org.apache.kafka.clients.producer.internals.Sender.failBatch(Sender.java:602)
> at org.apache.kafka.clients.producer.internals.Sender.sendProducerData(Sender.java:271)
> at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:221)
> at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:162)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)