[
https://issues.apache.org/jira/browse/CAMEL-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928143#comment-17928143
]
Sam commented on CAMEL-21757:
-----------------------------
Spring Kafka Handles it in a way of using transaction.id prefix where the
producer transactional.id is appended with n where n starts with 0 and is
incremented for new producer. During startup we can cache all the
transactional producers which will reduce our event processing but will
effectively help manage this.
I tried something like this at runtime but with workload increase the
Instatiating the transaction producer taking a lot of time with transaction
coordinator going down in some scenarios
> camel-kafka - Camel kafka Transactional ID with consumersCount>1 is not
> possible
> --------------------------------------------------------------------------------
>
> Key: CAMEL-21757
> URL: https://issues.apache.org/jira/browse/CAMEL-21757
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Affects Versions: 4.8.0
> Reporter: Sam
> Priority: Major
> Fix For: 4.8.4, 4.10.1, 4.11.0
>
>
> Kafka<-> with Kafka and with consumercount=24 So I am getting
> ProducerFencedException
>
> And as we are using
> additionaProperties[transactional.id]="transaction-producer"+UUID.randomUUID()
> enable.idempotence=true and retries=5 , we are also getting Invalid
> Transition attempted from state IN_TRANSACTION TO state IN_TRANSACTION
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
