You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/10/27 01:50:00 UTC

[jira] [Created] (KAFKA-6135) TransactionsTest#testFencingOnCommit may fail due to unexpected KafkaException

Ted Yu created KAFKA-6135:
-----------------------------

             Summary: TransactionsTest#testFencingOnCommit may fail due to unexpected KafkaException
                 Key: KAFKA-6135
                 URL: https://issues.apache.org/jira/browse/KAFKA-6135
             Project: Kafka
          Issue Type: Bug
            Reporter: Ted Yu


From https://builds.apache.org/job/kafka-pr-jdk9-scala2.12/2293/testReport/junit/kafka.api/TransactionsTest/testFencingOnCommit/ :
{code}
org.scalatest.junit.JUnitTestFailedError: Got an unexpected exception from a fenced producer.
	at org.scalatest.junit.AssertionsForJUnit.newAssertionFailedException(AssertionsForJUnit.scala:100)
	at org.scalatest.junit.AssertionsForJUnit.newAssertionFailedException$(AssertionsForJUnit.scala:99)
	at org.scalatest.junit.JUnitSuite.newAssertionFailedException(JUnitSuite.scala:71)
	at org.scalatest.Assertions.fail(Assertions.scala:1105)
	at org.scalatest.Assertions.fail$(Assertions.scala:1101)
	at org.scalatest.junit.JUnitSuite.fail(JUnitSuite.scala:71)
	at kafka.api.TransactionsTest.testFencingOnCommit(TransactionsTest.scala:319)
...
Caused by: org.apache.kafka.common.KafkaException: Cannot execute transactional method because we are in an error state
	at org.apache.kafka.clients.producer.internals.TransactionManager.maybeFailWithError(TransactionManager.java:782)
	at org.apache.kafka.clients.producer.internals.TransactionManager.beginCommit(TransactionManager.java:220)
	at org.apache.kafka.clients.producer.KafkaProducer.commitTransaction(KafkaProducer.java:617)
	at kafka.api.TransactionsTest.testFencingOnCommit(TransactionsTest.scala:313)
	... 48 more
Caused by: org.apache.kafka.common.errors.ProducerFencedException: Producer attempted an operation with an old epoch. Either there is a newer producer with the same transactionalId, or the producer's transaction has been expired by the broker.
{code}
Confirmed with [~apurva] that the above would not be covered by his fix for KAFKA-6119

Temporarily marking this as bug.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)