[
https://issues.apache.org/jira/browse/KAFKA-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380730#comment-17380730
]
Ewen Cheslack-Postava commented on KAFKA-3539:
----------------------------------------------
[~moses.nakamura] I spent a bunch of time on the clients in the past, but I've
barely been involved for the past few years. So not really even sure of the
current state of implementation and tests (e.g. I wasn't working on the clients
when EoS was implemented).
What tests fail due to minor changes? If they are unit tests, that should be
unexpected unless you are changing public API, which would require a KIP
anyway. You might also just be seeing flakiness in integration tests, which
unfortunately is expected. Providing a list of the tests that break and whether
it's compilation or runtime issues would probably help, but someone more active
can probably provide better guidance.
> 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)
