[
https://issues.apache.org/jira/browse/KAFKA-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353465#comment-17353465
]
Moses Nakamura edited comment on KAFKA-3539 at 5/28/21, 5:15 PM:
-----------------------------------------------------------------
I've gotten lots of good feedback on the discussion thread so far. [~cmccabe]
mentioned that there is a "fix" for the metadata case that means we don't need
to block, queue, or fail fast. That sounds better (and might avoid a breaking
change?), so I'd like to know more about that, but I think we have enough
information to start winnowing down the KIP to a more specific recommendation
once I understand that idea better.
was (Author: moses.nakamura):
I've gotten lots of good feedback on the discussion thread so far. [~cmccabe]
mentioned that there is a "fix" for the metadata case that means we don't need
to block, queue, or fail fast. That sounds better, so I'd like to know more
about that, but I think we have enough information to start winnowing down the
KIP to a more specific recommendation once I understand that idea 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
> Labels: needs-discussion, needs-kip
>
> 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
(v8.3.4#803005)
