[
https://issues.apache.org/jira/browse/KAFKA-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799776#comment-16799776
]
Steven Zhen Wu commented on KAFKA-3539:
---------------------------------------
just to echo last two comments.
There are many applications that just want best effort delivery to kafka and
can't tolerate blocking behavior at all. Now many people have to re-invent the
wheels to work around this problem. E.g. we implemented exactly the same things
that [~tu...@avast.com] mentioned.
Improved documentation can help. But an intuitive API is definitely much better.
> 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)
