Details
Description
The new (0.8.2 standalone) producer will block the first time it attempts to retrieve metadata for a topic. This is not the desired behavior in some use cases where async non-blocking guarantees are required and message loss is acceptable in known cases. Also, most developers will assume an API that returns a future is safe to call in a critical request path.
Discussing on the mailing list, the most viable option is to have the following settings:
pre.initialize.topics=x,y,z
pre.initialize.timeout=x
This moves potential blocking to the init of the producer and outside of some random request. The potential will still exist for blocking in a corner case where connectivity with Kafka is lost and a topic not included in pre-init has a message sent for the first time.
There is the question of what to do when initialization fails. There are a couple of options that I'd like available:
- Fail creation of the client
- Fail all sends until the meta is available
Open to input on how the above option should be expressed.
It is also worth noting more nuanced solutions exist that could work without the extra settings, they just end up having extra complications and at the end of the day not adding much value. For instance, the producer could accept and queue messages(note: more complicated than I am making it sound due to storing all accepted messages in pre-partitioned compact binary form), but you're still going to be forced to choose to either start blocking or dropping messages at some point.
I have some test cases I am going to port over to the Kafka producer integration ones and start from there. My current impl is in scala, but porting to Java shouldn't be a big deal (was using a promise to track init status, but will likely need to make that an atomic bool).
Attachments
Attachments
Issue Links
- is duplicated by
-
KAFKA-2120 Add a request timeout to NetworkClient
-
- Resolved
-
-
KAFKA-2137 New Kafka Producer not fully asynchronous
-
- Resolved
-
