[
https://issues.apache.org/jira/browse/KAFKA-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794810#comment-16794810
]
Michal Turek commented on KAFKA-3539:
-------------------------------------
Hi [~spyridon.ninos], ticket close won't fix the critical bug, so please no.
Our code base is full of multiple ugly workarounds that allow us live with this
broken behavior of Kafka producer without daily headache, but the situation
isn't good. Everyone with little higher request rate will soon or later
surprisingly hit this "Future must never block, since it essentially violates
the Future contract" bug. The producer implementation is just broken.
> KafkaProducer.send() may block even though it returns the Future
> ----------------------------------------------------------------
>
> Key: KAFKA-3539
> URL: https://issues.apache.org/jira/browse/KAFKA-3539
> Project: Kafka
> Issue Type: Bug
> Components: producer
> Reporter: Oleg Zhurakousky
> Priority: Critical
>
> You can get more details from the us...@kafka.apache.org by searching on the
> thread with the subject "KafkaProducer block on send".
> The bottom line is that method that returns Future must never block, since it
> essentially violates the Future contract as it was specifically designed to
> return immediately passing control back to the user to check for completion,
> cancel etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
