lightzhao opened a new issue, #4247:
URL: https://github.com/apache/incubator-seatunnel/issues/4247

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   When "semantics=EXACTLY_ONCE" is configured in kafkaSink, the data cannot be 
written successfully, and the checkpoint fails. The exception is as follows.
   1.[org.apache.kafka.common.errors.InvalidTxnStateException: The producer 
attempted a transactional operation in an invalid state.]
   2.[Transiting to fatal error state due to 
org.apache.kafka.common.errors.ProducerFencedException: There is a newer 
producer with the same transactionalId which fences the current one.]
   
   ### SeaTunnel Version
   
   2.3.0
   
   ### SeaTunnel Config
   
   ```conf
   kafka {
         topic = "test01"
         bootstrap.servers = "localhost:9092"
         semantics = EXACTLY_ONCE
     }
   ```
   
   
   ### Running Command
   
   ```shell
   bin/start-seatunnel-flink-connector-v2.sh -m yarn-cluster --config 
config/kafka_test
   ```
   
   
   ### Error Exception
   
   ```log
   1.[org.apache.kafka.common.errors.InvalidTxnStateException: The producer 
attempted a transactional operation in an invalid state.]
   2.[Transiting to fatal error state due to 
org.apache.kafka.common.errors.ProducerFencedException: There is a newer 
producer with the same transactionalId which fences the current one.]
   ```
   
   
   ### Flink or Spark Version
   
   flink 1.13.1
   
   ### Java or Scala Version
   
   _No response_
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to