Apurva Mehta commented on KAFKA-6446:

IMO, the right solution here would be for the producer to transition to a 
`FATAL_ERROR` state so that the only possible operation afterward is to 
`close()` the producer. In reality, if a `transactionalId` is specified, but 
the producer can't connect the cluster and initialize transactions, it should 
be able to do nothing else. Otherwise we risk violating transactional semantics.


> KafkaProducer with transactionId endless waits when bootstrap server is down
> ----------------------------------------------------------------------------
>                 Key: KAFKA-6446
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6446
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, producer 
>    Affects Versions:, 1.0.0
>            Reporter: Eduardo Sciullo
>            Priority: Critical
>         Attachments: Test.java
> When bootstrap server is down, a KafkaProducer with transactionId endless 
> waits on initTransactions. 
> The timeouts don't apply to that operation: don't honor the 
> Attached an example of my code to reproduce the scenario.
> I opened this issue as suggested by [Gary 
> Russell|https://stackoverflow.com/users/1240763/gary-russell]
> [https://stackoverflow.com/questions/48226546/defaultkafkaproducerfactory-with-transactionidprefix-endless-waits-when-bootstra]

This message was sent by Atlassian JIRA

Reply via email to