[ 
https://issues.apache.org/jira/browse/KAFKA-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049800#comment-16049800
 ] 

Apurva Mehta commented on KAFKA-5449:
-------------------------------------

With the latest patch, it appears that the producer which leaves its 
transaction open gets a producer fenced exception, while the produce which 
calls the commit gets the invalid transition exception: 

{noformat}
[2017-06-14 22:06:15,648] ERROR [TransactionalId transactional-producer] 
Aborting producer batches due to fatal error 
(org.apache.kafka.clients.producer.internals.Sender:384)
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
...
[2017-06-14 22:06:34,841] ERROR Uncaught error in kafka producer I/O thread:  
(org.apache.kafka.clients.producer.internals.Sender:164)
org.apache.kafka.common.KafkaException: [TransactionalId other] Invalid 
transition attempted from state READY to state ABORTABLE_ERROR
        at 
org.apache.kafka.clients.producer.internals.TransactionManager.transitionTo(TransactionManager.java:477)
        at 
org.apache.kafka.clients.producer.internals.TransactionManager.transitionToAbortableError(TransactionManager.java:289)
        at 
org.apache.kafka.clients.producer.internals.Sender.failBatch(Sender.java:604)
        at 
org.apache.kafka.clients.producer.internals.Sender.sendProducerData(Sender.java:272)
        at 
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:223)
        at 
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:162)
{noformat}

Very strange. Unfortunately I changed the wrong log4j.properties, so we didn't 
get the trace logging for that failure.

> Flaky test TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-5449
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5449
>             Project: Kafka
>          Issue Type: Bug
>          Components: core, unit tests
>            Reporter: Matthias J. Sax
>            Assignee: Apurva Mehta
>              Labels: exactly-once, test
>
> {noformat}
> java.lang.AssertionError: Consumed 6 records until timeout instead of the 
> expected 8 records
>       at kafka.utils.TestUtils$.fail(TestUtils.scala:333)
>       at kafka.utils.TestUtils$.waitUntilTrue(TestUtils.scala:847)
>       at kafka.utils.TestUtils$.consumeRecords(TestUtils.scala:1357)
>       at 
> kafka.api.TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData(TransactionsTest.scala:143)
> {noformat}



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

Reply via email to