[jira] [Comment Edited] (KAFKA-13267) InvalidPidMappingException: The producer attempted to use a producer id which is not currently assigned to its transactional id

["Matthias J. Sax (Jira)" <ji...@apache.org>]

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

Matthias J. Sax edited comment on KAFKA-13267 at 9/14/21, 4:35 PM:
-------------------------------------------------------------------

According to [KIP-691|https://cwiki.apache.org/confluence/display/KAFKA/KIP-691%3A+Enhance+Transactional+Producer+Exception+Handling], {{InvalidPidMappingException}} should actually be considered non-fatal, and we might want to try to handle it within Kafka Streams.


was (Author: mjsax):
According to [KIP-671|https://cwiki.apache.org/confluence/display/KAFKA/KIP-671%3A+Introduce+Kafka+Streams+Specific+Uncaught+Exception+Handler], {{InvalidPidMappingException}} should actually be considered non-fatal, and we might want to try to handle it within Kafka Streams.

> InvalidPidMappingException: The producer attempted to use a producer id which is not currently assigned to its transactional id
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-13267
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13267
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.8.0
>            Reporter: Gilles Philippart
>            Priority: Major
>
> We're using Confluent Cloud and Kafka Streams 2.8.0 and we've seen these errors pop up in apps using EOS:
> {code:java}
> InvalidPidMappingException: The producer attempted to use a producer id which is not currently assigned to its transactional id
> {code}
> Full stack trace:
> {code:java}
> Error encountered sending record to topic ola-update-1 for task 4_7 due to: org.apache.kafka.common.errors.InvalidPidMappingException: The producer attempted to use a producer id which is not currently assigned to its transactional id. Exception handler choose to FAIL the processing, no more records would be sent.
> RecordCollectorImpl.java  226  recordSendError(...)
> RecordCollectorImpl.java:226:in `recordSendError'
> RecordCollectorImpl.java  196  lambda$send$0(...)
> RecordCollectorImpl.java:196:in `lambda$send$0'
> KafkaProducer.java  1365  onCompletion(...)
> KafkaProducer.java:1365:in `onCompletion'
> ProducerBatch.java  231  completeFutureAndFireCallbacks(...)
> ProducerBatch.java:231:in `completeFutureAndFireCallbacks'
> ProducerBatch.java  159  abort(...)
> ProducerBatch.java:159:in `abort'
> RecordAccumulator.java  763  abortBatches(...)
> RecordAccumulator.java:763:in `abortBatches'
> More (5 lines)
> Nested Exceptionsorg.apache.kafka.streams.errors.StreamsException: Error encountered sending record to topic ola-update-1 for task 4_7 due to: org.apache.kafka.common.errors.InvalidPidMappingException: The producer attempted to use a producer id which is not currently assigned to its transactional id. Exception handler choose to FAIL the processing, no more records would be sent.
> RecordCollectorImpl.java  226  recordSendError(...)
> RecordCollectorImpl.java:226:in `recordSendError'
>  org.apache.kafka.common.errors.InvalidPidMappingException: The producer attempted to use a producer id which is not currently assigned to its transactional id.
> {code}
> I've seen that KAFKA-6821 described the same problem on an earlier version of Kafka and was closed due to the subsequent works on EOS.
> Another ticket raised recently shows that the exception is still occurring (but the ticket wasn't raised for that specific error): KAFKA-12774



--
This message was sent by Atlassian Jira
(v8.3.4#803005)